Navicat user management compatibility

[dveeden]

Bug Report

Try to manage users in TiDB with Navicat

1. Minimal reproduce step (Required)

With Navicat 16.2.2 click the "User" button.

2. What did you expect to see? (Required)

User management

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

Release Version: v7.2.0
Edition: Community
Git Commit Hash: 9fd5f4a8e4f273a60fbe7d3848f85a1be8f0600b
Git Branch: heads/refs/tags/v7.2.0
UTC Build Time: 2023-06-27 15:04:42
GoVersion: go1.20.5
Race Enabled: false
Check Table Before Drop: false
Store: tikv

[dveeden]

This fixes it. Note that changing the definition of mysql.user is not supported and should not be done in production. This is only for debugging.

mysql> ALTER TABLE mysql.user ADD COLUMN `ssl_type` enum('','ANY','X509','SPECIFIED') NOT NULL DEFAULT '';
Query OK, 0 rows affected (0.04 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `ssl_cipher` blob NOT NULL;
Query OK, 0 rows affected (0.05 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `x509_issuer` blob NOT NULL;
Query OK, 0 rows affected (0.08 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `x509_subject` blob NOT NULL;
Query OK, 0 rows affected (0.05 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `max_questions` int unsigned NOT NULL DEFAULT '0';
Query OK, 0 rows affected (0.07 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `max_updates` int unsigned NOT NULL DEFAULT '0';
Query OK, 0 rows affected (0.09 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `max_connections` int unsigned NOT NULL DEFAULT '0';
Query OK, 0 rows affected (0.09 sec)

mysql> ALTER TABLE mysql.user ADD COLUMN `max_user_connections` int unsigned NOT NULL DEFAULT '0';
Query OK, 0 rows affected (0.06 sec)

[bb7133]

Thanks for reporting this, I found another (old) issue for this: #9655