Database Support
Understand which databases DBX can connect to and which advanced features are available per engine.
DBX uses native Rust drivers for the main app whenever possible. Some engines are compatibility profiles over MySQL or PostgreSQL protocols, and some are handled through Agent drivers or the optional JDBC Plugin.
Connection Profiles
The connection dialog exposes ready-to-use profiles with default ports and driver labels.
| Group | Profiles | Notes |
|---|---|---|
| Core SQL engines | MySQL, PostgreSQL, SQLite, DuckDB, ClickHouse, SQL Server, Oracle, Redshift, DM, GaussDB | Available directly in the DBX connection picker |
| Document and key-value engines | Redis, MongoDB, Elasticsearch | Use dedicated browsers or query flows instead of the generic relational grid where appropriate |
| MySQL-compatible profiles | MariaDB, TiDB, OceanBase, Doris, SelectDB, StarRocks, GoldenDB, custom MySQL | Reuse MySQL-style connection handling where the engine speaks a compatible protocol |
| PostgreSQL-compatible profiles | openGauss, KingBase, HighGo, Vastbase, CockroachDB, custom PostgreSQL | Reuse PostgreSQL-style connection handling where the engine speaks a compatible protocol |
| File-based engines | SQLite, DuckDB, Microsoft Access | Choose a local database file instead of host and port |
| Agent/JDBC-oriented engines | H2, Snowflake, Trino, Hive, DB2, Informix, Neo4j, Cassandra, BigQuery, Kylin, SunDB, TDengine, JDBC | Feature coverage depends on the driver path used by that engine |
Default Ports
| Profile | Default Port |
|---|---|
| MySQL / MariaDB / GoldenDB | 3306 |
| PostgreSQL / openGauss / GaussDB / Vastbase | 5432 |
| Redis | 6379 |
| MongoDB | 27017 |
| ClickHouse | 8123 |
| SQL Server | 1433 |
| Oracle | 1521 |
| Elasticsearch | 9200 |
| TiDB | 4000 |
| OceanBase | 2881 |
| Doris / SelectDB / StarRocks | 9030 |
| Redshift | 5439 |
| CockroachDB | 26257 |
| DM | 5236 |
| KingBase | 54321 |
| HighGo | 5866 |
| H2 | 9092 |
| Snowflake | 443 |
| Trino | 8080 |
| Hive | 10000 |
| DB2 | 50000 |
| Informix | 9088 |
| Neo4j | 7687 |
| Cassandra | 9042 |
| BigQuery | 443 |
| Kylin | 7070 |
| SunDB | 22000 |
| TDengine | 6041 |
SQLite, DuckDB, Access, and JDBC profiles use port 0 in the saved connection model when a network port is not part of the connection.
Feature Matrix
DBX intentionally enables advanced workflows only where the app has enough metadata and SQL-generation support.
| Feature | Supported Types |
|---|---|
| Schema-aware tree | PostgreSQL, SQL Server, Oracle, Redshift, DM, GaussDB, KingBase, HighGo, Vastbase, JDBC, H2, Snowflake, Trino, DB2, TDengine |
| ER diagram | MySQL, PostgreSQL, SQLite, SQL Server, Oracle, Redshift, DM, GaussDB, KingBase, HighGo, Vastbase, GoldenDB, Access, H2, DB2 |
| Database search | MySQL, PostgreSQL, SQLite, SQL Server, Oracle, Redshift, DuckDB, ClickHouse, DM, GaussDB, KingBase, HighGo, Vastbase, GoldenDB, Access, H2, Snowflake, Trino, Hive, DB2, Informix, Neo4j, Cassandra, BigQuery, Kylin, SunDB, TDengine |
| Table import | MySQL, PostgreSQL, SQLite, DuckDB, ClickHouse, SQL Server, Oracle, Doris, StarRocks, Redshift, DM, GaussDB, KingBase, HighGo, Vastbase, GoldenDB, Access |
| Table structure editor | MySQL, PostgreSQL, SQLite, SQL Server |
| Create database | MySQL, PostgreSQL, SQL Server, ClickHouse, Oracle, DM, GaussDB, Doris, StarRocks, Redshift |
| Field lineage | MySQL, PostgreSQL, SQLite, SQL Server, Oracle, Redshift, DM, GaussDB |
| Data transfer | MySQL, PostgreSQL, SQLite, SQL Server, Oracle, ClickHouse, DuckDB, DM, GaussDB |
| SQL file execution unavailable | Redis, MongoDB, Elasticsearch |
If a database can connect but does not appear in a feature row, that feature may be hidden or limited for that engine. This prevents DBX from generating SQL it cannot review reliably.
Connection Options
Most network databases support host, port, username, password, default database, optional URL parameters, SSL, connection color, SSH tunnel, and proxy settings. File-based engines replace host and port with a file picker.
DBX can also parse common connection URLs for engines such as MySQL, PostgreSQL, Redis, MongoDB, ClickHouse, SQL Server, Oracle, Elasticsearch, DM, GaussDB, openGauss, TDengine, and Access.
DM And ODBC
DM uses an ODBC-based path and requires the DM ODBC driver installed on the machine running DBX.
sudo apt install unixodbc
# Install DM8, which includes the ODBC driver.
# Download from https://eco.dameng.com/download/
sudo tee -a /etc/odbcinst.ini << 'EOF'
[DM8 ODBC DRIVER]
Description = DM8 ODBC Driver
Driver = /opt/dmdbms/bin/libdodbc.so
EOFThe DM installer normally registers the ODBC driver automatically.
DM does not provide a native macOS ODBC driver. Use a Linux host for DM development or testing when possible.
Extending Support
Use the JDBC Plugin when a database is not covered by the built-in profiles or when your team must use a vendor JDBC driver. JDBC keeps vendor driver JARs outside the main DBX app, so you control which driver files are installed.