Feature : Support TiDB

Please confirm that the bug report does not already exist

• I confirm there is no existing issue for this bug.

Steps to reproduce

1. Go to 'Base Integrations' -> 'Add New Data Source' -> Select 'MySQL'.
2. Fill in connection details for a TiDB Cloud / Vitess instance (e.g., Host: gateway01.us-east-1.prod.aws.tidbcloud.com, Port: 4000).
3. Test or save the connection.
4. Error appears: "Vitess/PlanetScale/TiDB is not supported" or "Unknown SSL profile 'true'".

Desired Behavior

NocoDB should not artificially block wire-compatible MySQL engines like TiDB, PlanetScale, or Vitess.

1. Protocol Compatibility: TiDB is fully MySQL 8.0 wire-compatible. Blocking it based solely on server version banners restricts developers from using highly available, free-tier cloud-native databases (e.g., TiDB Serverless with 25GB free tier).
2. SSL Parameter Parsing: When using standard MySQL SSL connection strings or UI toggles, NocoDB's driver throws Unknown SSL profile 'true' instead of properly passing SSL flags down to the Knex/mysql2 driver.
3. Request: Please allow users to bypass or disable the strict server version check, or gracefully handle standard MySQL-compatible dialects so we are not forced to pay for expensive proprietary managed MySQL instances.

Project Details

NocoDB used as docker : true NocoDB version : latest Database used in NC_DB URL : pg Project was created by clicking : New Project by connecting to external database Database on which spreadsheet is created : mysql (TiDB Cloud) OS on which NocoDB is running : Linux Node.js version if running as node : N/A (Docker) Database version : TiDB v8.5 / MySQL 8.0 Compatible

Attachments