Versions

Compare two versions

The comparison page answers “what changed between these two versions?” It groups changes by object type, marks each one as added, modified, or removed, and shows a line-by-line diff of any SQL body that changed.

In the app: Data Model › Schemas › your schema › Versions › tick two versions › Compare Diff

[screenshot]
The Comparing Versions page with the Tables section open: one ADDED table, one MODIFIED table with its column changes, and a view script diff below.

Open the comparison

  1. Open the schema’s Versions page.
  2. Tick the checkboxes on two version cards.
  3. Click Compare Diff.

The page always compares the older version to the newer one, whichever order you ticked them in. While it works you see Comparing versions....

Read the header

The header reads Comparing Versions, followed by the two version badges with an arrow between them (for example v1.0.0 → v1.1.0) and the two creation dates. A one-line summary of the changes sits underneath. Back to Versions returns you to the list.

Read the sections

Changes are grouped into sections. A section appears only when it has changes, and each shows a count badge.

Section What’s inside each changed item
Tables Changed table properties, then Columns (n) and Indexes (n) with their own changes
Views Changed properties, Output Columns (n), Parameters (n), and one script diff per dialect
Stored Procedures Same as Views
Functions Same as Views
Enums Changed enum properties, then Values (n)

Every changed item is a card with a coloured left border and a badge:

  • ADDED (green): exists only in the newer version.
  • MODIFIED (orange): exists in both, but something about it changed.
  • REMOVED (red): exists only in the older version.

Sections open expanded. Click a section header to collapse it.

Note: Standalone scripts are not included in the comparison.

Property changes

A modified item lists each changed property on one line, in the form Property: old → new. The old value is struck through in red and the new value is in green. A dash (—) stands for an empty value. For example, a column whose type widened shows its old and new data type side by side.

An added item shows a compact summary of its properties instead. A removed item shows only its name.

Script diffs

Views, procedures, and functions keep a separate SQL body per dialect, so the diff has one block per dialect that changed. Each block is labelled Script: <dialect> with its own ADDED, MODIFIED, or REMOVED badge.

  • A new script is shown entirely in green.
  • A removed script is shown entirely in red and struck through.
  • A changed script is shown inline with line numbers. Added lines are green and marked +, removed lines are red and marked -, and changed lines are marked ~.

What to do next

  • Review the scope of a release before you deploy it.
  • Generate a migration script between the same two versions to apply the changes to a database. See Generate a migration script.
  • Enum changes are not written into migration scripts automatically. Use this page to see them and apply them by hand.