Schema diff

QoreDB Pro compares database schemas and turns the differences into migrations. It works in three ways: generate a migration from a saved baseline, detect drift against that baseline, and compare two connections side by side.

The feature is gated by isFeatureEnabled('schema_diff'); without a Pro license the entry points show an upgrade prompt instead of running.

Migration from a baseline

Capture a baseline — a snapshot of a connection's schema — then let QoreDB diff the live schema against it and produce a migration. Both an up and a down script are generated by the DDL builders. Operations that can't be reversed (a dropped column or table, for example) are flagged as irreversible rather than guessed at.

QoreDB refuses to emit a migration it can't produce faithfully: an incomplete capture, or a change the target dialect can't express (for instance an in-place column type change on SQLite), is reported instead of being written out as a half-migration.

Drift detection

Drift detection compares the live schema against the baseline persisted on disk. Baselines live under .qoredb/baselines/, one entry per connection, and the folder is git-ignored — it's local state, not something you commit. If the live schema has moved away from the baseline, the drift is surfaced so you can regenerate a migration or update the baseline.

Comparing two connections

From a table's context menu you can compare the schema of two connections in one click — the Prod↔Staging case. The comparison covers tables, columns, indexes, foreign keys and the primary key, listing what differs between the two.

Where to go next

• Migration generation for data-change migrations captured in the sandbox
• Data diff for comparing row contents rather than structure
• Pricing to see what's included in Pro