KS DB Merge Tools logo KS DB Merge Tools
Documentation
KS DB Merge Tools for PostgreSQL logo for PostgreSQL
 
KS DB Merge Tools for Oracle logo
KS DB Merge Tools for MySQL logo
MssqlMerge logo
KS DB Merge Tools for SQLite logo
AccdbMerge logo
KS DB Merge Tools for Cross-DBMS logo

Schema Merge Options Dialog

This dialog is opened when you merge tables in the Object list or Table structure diff tabs and the merge includes new NOT NULL columns without DEFAULT values. This operation may fail if the target table already contains data. It is also opened when you merge tables in the Object list and the target tables have partitions that do not exist in the source tables. Only the groups that apply to the merge are shown.

for PostgreSQL, schema merge options dialog

The dialog contains the following options:

New NOT NULL columns without DEFAULT

This section provides information about the issue and available solutions:

You are about to merge table(s) that include new NOT NULL column(s) without defaults. This operation may fail if the target table already contains data. To prevent this, you can either remove the NOT NULL constraint or specify a DEFAULT value. Then you can merge data and run table definition merge again to resolve any remaining NOT NULL or DEFAULT differences.

WARNING: Default value can be set for only one column. The DEFAULT expression you enter will be used as is, without SQL injection protection.

The dialog offers the following radio button options:

  • Keep NOT NULL
    Keep the NOT NULL constraint on the column(s). This may cause the merge to fail if the target table contains existing rows.
  • Remove NOT NULL
    Remove the NOT NULL constraint from the column(s). This allows the merge to proceed without requiring a DEFAULT value.
  • Add DEFAULT
    Add a DEFAULT value for the column. This option is available only when merging a single NOT NULL column without DEFAULT. Enter the DEFAULT expression in the text field next to this option.

Target partitions missing in source

This group is shown when the 'Partitions' option is enabled in Settings and some of the selected tables have partitions in the target database only:

Some of the selected tables have partitions in the target database that do not exist in the source database. Choose what to do with them.

Radio button options:

  • Drop (data is lost) - drop these partitions with their data.
  • Detach (data is kept, tables are shown as new) - detach these partitions from the parent table. They stay in the target database as regular tables, and the Object list shows them as new tables.
  • Keep attached (table can stay changed) - the default. These partitions are not changed, so the table can still be shown as changed after the merge. A new partition from the source can fail if its bound overlaps a kept partition.
  • Skip all partition changes (table can stay changed) - do not merge any partition changes of the existing tables. New tables are still created with their partitions.

The choice is not saved, so the dialog always opens with Keep attached selected.

After selecting an option, click OK to proceed with the merge or Cancel to abort the operation.


Last updated: 2026-10-23