Supported Databases
Use this catalog to choose the source type for your connection and check its main workflows. CE connects to SQL databases, local database files, document stores, caches, and search systems.
Choose the entry matching the actual product when one is available. Compatible entries share a connector family, but differences in the server can still affect syntax, metadata, and supported operations. Test the queries and changes you need against your own source version.
Choose a source type#
| Database Type | Family Used By WhoDB | Connection Style | Scratchpad | Mock Data | Notes |
|---|---|---|---|---|---|
Postgres | PostgreSQL | Network | Yes | Yes | Schema-aware SQL flow |
CockroachDB | PostgreSQL-compatible | Network | Yes | Yes | Uses PostgreSQL-family behavior |
YugabyteDB | PostgreSQL-compatible | Network | Yes | Yes | Uses PostgreSQL-family behavior |
QuestDB | PostgreSQL-compatible | Network | Yes | Yes | Reduced schema/database switching vs core PostgreSQL |
MySQL | MySQL | Network | Yes | Yes | Uses database switching instead of schemas |
MariaDB | MySQL-compatible | Network | Yes | Yes | Uses MySQL-family behavior |
TiDB | MySQL-compatible | Network | Yes | Yes | Uses MySQL-family behavior |
SQLite3 | SQLite | File path | Yes | Yes | File-backed connection |
DuckDB | DuckDB | File path | Yes | Yes | Available only on supported builds |
ClickHouse | ClickHouse | Network | Yes | Yes | Analytical SQL workflow |
MongoDB | MongoDB | Network | Yes | Yes | Scratchpad uses shell-style commands (e.g. db.collection.find({})) instead of SQL |
FerretDB | MongoDB-compatible | Network | Yes | Yes | Uses MongoDB-family behavior |
DocumentDB | MongoDB-compatible | Network | Yes | Yes | AWS-managed catalog entry |
Redis | Redis | Network | Yes | No | Scratchpad uses Redis commands (e.g. TYPE key) instead of SQL |
Valkey | Redis-compatible | Network | Yes | No | Uses Redis-family behavior |
Dragonfly | Redis-compatible | Network | Yes | No | Uses Redis-family behavior |
ElastiCache | Redis-compatible | Network | Yes | No | AWS-managed catalog entry |
Memcached | Memcached | Network | No | No | Cache/key browsing workflow |
ElasticSearch | ElasticSearch | Network | No | No | Search/index workflow |
OpenSearch | ElasticSearch-compatible | Network | No | No | Uses ElasticSearch-family behavior |
Understand the differences#
Managed cloud variants
DocumentDB and ElastiCache are marked as AWS-managed catalog entries. They can be introduced through configured profiles or opt-in CLI discovery; they are not ordinary choices in the web credential form.
Local database files
SQLite3 and DuckDB use a database file path instead of host and port fields. The file must be accessible to the WhoDB process. In Docker, mount its directory and enter the container path. The desktop app offers a native file picker.
Available operations
Not every database type exposes the same feature set:
- SQL-capable databases generally support Scratchpad, graph/schema views, and mock data generation
- MongoDB-family and Redis-family systems support Scratchpad using their native command syntax rather than SQL
- Memcached and search systems use narrower capability sets
- Database switching and schema support vary by family
Build availability
DuckDB availability depends on the build target. Check that it appears in the connection form for the artifact you installed before planning a file-based workflow around it.
Connection profiles#
Profiles use WHODB_<TYPE> JSON arrays or numbered variables such as WHODB_POSTGRES_1. The type name is uppercased. Cloud-managed entries also accept this profile pattern; local CLI discovery is another way to find their endpoints.
See Installation for examples and shared-profile access implications.
Connect the source#
Was this page helpful?