Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: navicat连接到tidb数据库 报Unknown column ‘ssl_type’ in ‘field list’
[TiDB Usage Environment] Production Environment
[TiDB Version] v7.1.0
[Reproduction Path] No operations performed, encountered this issue upon taking over
[Encountered Problem: Phenomenon and Impact] Upon entering the TiDB database, this error is reported. Clicking on the user, the user information cannot be viewed, and an error is displayed. Could the experts please help to identify the issue and suggest which MySQL command can be used to find this field?
[Resource Configuration] *
[Attachment: Screenshot/Log/Monitoring]
The cause of this error is that MySQL uses the ssl_type (and other related columns) in the mysql.user table to store user authentication information. For certain reasons, TiDB stores the ssl_type information in a newly added table called mysql.global_priv. Typically, similar management tools use syntax like SHOW GRANTS to obtain permission information, but Navicat directly queries the internal table, leading to this compatibility issue.
To fix this problem, some compatibility adjustments are needed. If there are any updates, we will notify you in the post.
Which version of Navicat are you using? I’ve never had any issues connecting.
Switch to 16. We all use 16 without any issues.
Using version 15 is no problem. For the final open-source issue, I still used DBeaver for convenience.
Navicat is not allowed to be used by the company.
Is it a version issue? Please confirm and let us take a look.
We did the same, finally abandoned Navicat and chose DBeaver.
Yes, DBeaver can do it. Even the latest version of Navicat will encounter this error.
It’s not a version issue. I downloaded a new version 16, and the problem still occurs, but DBeaver works fine.
I’ve used Navicat for many years, switching to DBeaver makes everything difficult to understand.
Use DBeaver, there are no authorization issues yet.
Yes, at first I wasn’t used to it either, but after using it for a while, I can only say it’s great~
So far, this issue has not been found in Navicat 15 and above.
So far, this issue has not been found in Navicat 15 and above.
This issue should not occur if you use version 15 or above, or you can use DBeaver.
|
username: TiDBer_j9d3wEwH
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
Welcome back~
|
username: 
|
username: