Visualize QuestDB's Timestamp and Partition Columns

Connect DbSchema to QuestDB and turn the live schema into an editable visual model: explore relationships in interactive ER diagrams, plan changes on the canvas, and generate reviewed SQL scripts for deployment.

The workflow is designed for visual modeling, schema documentation, and deployment — keep an offline model in Git, collaborate across teams, and publish documentation that developers, analysts, and stakeholders can navigate in minutes.

Download DbSchema See QuestDB Features Download QuestDB JDBC Driver · All drivers

QuestDB is a columnar, append-only time-series database built for high-throughput ingestion and low-latency analytical queries. Its storage engine is purpose-built for time-ordered data, and every table has a designated timestamp column that drives partition layout. QuestDB exposes a PostgreSQL wire protocol endpoint, which means DbSchema connects using the standard PostgreSQL JDBC driver and interacts with QuestDB's SQL dialect without any custom adapter.

Write SQL Queries Against QuestDB Tables

QuestDB extends ANSI SQL with time-series operators including SAMPLE BY, LATEST ON, and ASOF JOIN. DbSchema's SQL editor accepts these extensions, letting you write and execute time-series queries interactively, inspect column types, and iterate on results without switching tools.

Download DbSchema Free See QuestDB Features

Browse Time-Series Rows in the Data Explorer

The data explorer renders QuestDB query results in a paginated grid with column-level filtering. Use it to spot-check recently ingested data, verify timestamp precision after a write, or confirm that an expected row exists — without writing a one-off query client.

Document QuestDB Table Schemas

DbSchema generates static HTML documentation from the QuestDB schema, listing each table with its column names, data types, and designated timestamp column. Share this documentation with teams consuming QuestDB data via InfluxDB Line Protocol or the REST API so they understand the expected schema before writing ingest code.

Connect DbSchema to a QuestDB Table Store

QuestDB speaks PostgreSQL wire protocol, so the connection wizard looks like a standard PostgreSQL setup with one port difference to remember.

1. Install DbSchema and start a new connection.
2. Select PostgreSQL as the database type — DbSchema downloads the PostgreSQL JDBC driver automatically.
3. Enter the host and port 8812, QuestDB's PostgreSQL wire protocol listener (not the default PostgreSQL port), forming the URL jdbc:postgresql://host:8812/qdb.
4. Log in with the default credentials — username admin, password quest — or your own if you've changed them, which any production deployment should do.
5. Connect. DbSchema reads the designated timestamp and partition columns into the ER diagram.

QuestDB also exposes a REST API on port 9000 and an InfluxDB Line Protocol ingress on port 9009, but those are ingest-only interfaces — DbSchema uses only the PG wire protocol endpoint at port 8812.

Why Time-Series Teams Add DbSchema to QuestDB

• Visualize QuestDB table schemas including designated timestamp and partition columns
• Run SAMPLE BY, LATEST ON, and ASOF JOIN queries from a dedicated SQL editor
• Page through ingested time-series data without writing a separate client application
• Generate schema documentation for API consumers and downstream analytics teams
• Compare table schemas across QuestDB instances in different environments

Ingesting through the InfluxDB Line Protocol or REST API and want a schema view to match? Download DbSchema and document every QuestDB table's timestamp and partition columns for the teams consuming your data.

Related databases

Teams working with QuestDB often use these engines too. Explore dedicated guides and JDBC setup for each.

• Amazon Athena
• Amazon Timestream
• Azure Synapse
• ClickHouse
• Databricks
• Dataverse

Browse all 100+ supported databases