Problem
TiDB speaks the MySQL protocol, so it connects through the MySQL plugin, but it is not a first-class type. Its own catalog tables, its cluster topology and its differences from MySQL are invisible, and version detection reports it as MySQL.
Proposed solution
- A
DatabaseType of its own, detected from VERSION() containing TiDB, with its own icon and defaults.
- TiDB-specific catalog in the sidebar where it differs: cluster info, regions, and
INFORMATION_SCHEMA.CLUSTER_*.
- Suppress the MySQL features TiDB does not have, rather than offering them and failing.
- Its own docs page saying what works and what does not.
Alternatives considered
Connect as MySQL and accept the mismatches.
Related database type
MySQL / MariaDB
Problem
TiDB speaks the MySQL protocol, so it connects through the MySQL plugin, but it is not a first-class type. Its own catalog tables, its cluster topology and its differences from MySQL are invisible, and version detection reports it as MySQL.
Proposed solution
DatabaseTypeof its own, detected fromVERSION()containing TiDB, with its own icon and defaults.INFORMATION_SCHEMA.CLUSTER_*.Alternatives considered
Connect as MySQL and accept the mismatches.
Related database type
MySQL / MariaDB