Skip to content

Latest commit

 

History

History
91 lines (78 loc) · 4.36 KB

index.mdx

File metadata and controls

91 lines (78 loc) · 4.36 KB
title Supported Databases
description All 47 engines TablePro connects to, their default ports, and which ones need a plugin

import DriverCounts from "/snippets/driver-counts.mdx";

Forty-seven engines, and every one of them is free to use. What differs between them is where the driver comes from, not what the license covers.

The full list

Database Default port Driver
Amazon Redshift 5439 Built-in
Beancount File-based Plugin
BigQuery API-based Plugin
Bigtable API-based Plugin
Cassandra 9042 Plugin
ClickHouse 8123 Built-in
Cloudflare D1 API-based Plugin
Cloudflare R2 SQL API-based Plugin
CockroachDB 26257 Built-in
Dameng DM8 5236 Plugin
Databend 3307 Built-in
DuckDB File, or 9494 remote Plugin
DynamoDB API-based Plugin
Elasticsearch 9200 Plugin
etcd 2379 Plugin
Firebase Realtime Database API-based Plugin
Firestore API-based Plugin
InfluxDB 8086 Plugin
KingbaseES 54321 Plugin
libSQL API-based Plugin
Kafka 9092 Plugin
MariaDB 3306 Built-in
Memcached 11211 Plugin
Microsoft SQL Server 1433 Plugin
MongoDB 27017 Plugin
MySQL 3306 Built-in
Neo4j 7687 Plugin
OceanBase 2881 Built-in
Oracle Database 1521 Plugin
PGlite 5432 Built-in
PostgreSQL 5432 Built-in
Presto 8080 Plugin
Qdrant 6333 Plugin
Redis 6379 Built-in
SAP HANA 443 Plugin
ScyllaDB 9042 Plugin
Snowflake 443 Plugin
Spanner API-based Plugin
StarRocks 9030 Plugin
SQLite File-based Built-in
SurrealDB 8000 Plugin
Teradata 1025 Plugin
TiDB 4000 Built-in
Trino 8080 Plugin
Typesense 8108 Plugin
Turso API-based Plugin
Weaviate 8080 Plugin

Rows sharing a page share a driver. MariaDB reads as MySQL, ScyllaDB as Cassandra, Turso as libSQL, Presto as Trino, and Redshift, CockroachDB and PGlite all speak the PostgreSQL wire protocol. TiDB, Databend and OceanBase also run on the bundled MySQL driver.

Built-in against plugin

A built-in driver is already in the app and connects with nothing else installed. A plugin is a signed bundle TablePro fetches the first time you pick that engine, before the connection form opens and without a restart. After that the two behave the same: same grid, same editor, same export.

The split is about size, not capability. Bundling every client library would put hundreds of megabytes of Oracle and MongoDB code in an app most people use for one database.

Plugins update on their own schedule, so a driver fix can reach you without waiting for an app release. Plugins covers installing, updating and removing them.

When yours is not here

Two of these engines already stand in for others. Anything that speaks the PostgreSQL or MySQL wire protocol will usually connect through those drivers, including managed services that never say so: Neon, Supabase, Heroku, Aurora and Cloud SQL all work this way. Point the connection at the host they give you.

If it speaks neither, open a request on GitHub. Drivers are plugins, so a new one is a bundle rather than a new version of the app.