Table Structure Diff Tab
- Opened from: Object list, Data diff and Text diff tabs
- Applicable tab-specific toolbar actions:
- Jump to the
last,
next,
previous,
first change
- Select
all,
none,
invert selection on the left,
all,
none,
invert selection on the right side
Export to Xlsx or Json
- Applicable object types: Tables
This tab allows to compare definition of particular table:
Here is explanation of changes highlight annotation on the above screenshot:
- 1 Changed item ("store_id" which has changed Nullability)
- 2 New item ("activebool")
- 3 Unchanged column with changed column order ("email")
- 4 Changed column with changed column order ("active" has changed nullablity)
Vertical toolbar between two panels contains additional tab-specific actions:
The tab has three sections: Columns, Constraints and Conversion errors. Each section can be collapsed. Some grid columns are shown only if one of the databases is marked as Target schema in the Open databases dialog. In the grid column names below, {target DBMS} is the name of that DBMS, for example Type (PostgreSQL). A table can't be merged from this tab: new tables are merged from the Object list.
Columns
- Name - column name. Columns are matched by name, ignoring case
- Nullability - NULL or NOT NULL
- Type (generic) - generic data type of the column, see Data types
- Type (native) - data type as the database reports it. It is shown for information: a different native type is not counted as a change
- Type ({target DBMS}) - only with Target schema. For the other database, it is the column data type converted to the target DBMS, the type that the schema merge creates. For the target database, it is the column's own type in the same normalized form. Empty if the type can't be converted (see Conversion errors below)
- Type status - only with Target schema, for a column that exists in both tables. It shows how the converted type of the source column relates to the target column type, the same way as Data diff compares their values (see How it works - Data):
- Same - the same data type
- Compatible - another data type that the data can be compared with and merged into. It can be equivalent (the same values with another type name), wider (the target holds every source value) or narrower (some source values may not fit, the data merge dialog warns about it)
- Incompatible - the data of this column is not compared and not merged
The status is the same on both sides and is not counted as a change itself
- Autoinc - auto-increment (identity) column
- Default (native) - default value expression as the database reports it, shown for information
- Default ({target DBMS}) - only with Target schema: default value expression converted to the target DBMS syntax
- Generated (native) - generated (computed) column expression as the database reports it, shown for information
- Generated ({target DBMS}) - only with Target schema: generated column expression converted to the target DBMS syntax
- Generated STORED - Yes if the generated column value is stored, No if it is virtual
A column is highlighted as changed if it has a different Nullability, Type (generic), Autoinc or Generated STORED value. With Target schema, a different Type ({target DBMS}), Default ({target DBMS}) or Generated ({target DBMS}) value is a change too.
Constraints
- Type - PRIMARY KEY, UNIQUE or CHECK
- Columns - constraint columns
- Name - constraint name, shown for information
- Definition (native) - CHECK constraint expression as the database reports it, shown for information
- Definition ({target DBMS}) - only with Target schema: CHECK constraint expression converted to the target DBMS syntax
A constraint is highlighted as changed if it has a different type or columns, and with Target schema a different Definition ({target DBMS}).
Conversion Errors
This section has rows only with Target schema, for the table of the other (not target) database. It lists the table items that can't be converted into the target DBMS:
- Error type - Column type, Column default, Column generated as or Constraint check
- Expression - the data type or expression that can't be converted
The Object list shows the number of these errors in the Err column. When a table with conversion errors is merged, the Schema merge options dialog asks whether to merge it anyway and skip the failed columns, properties and objects.
Last updated: 2026-11-18