Skip to main content
Comparing

Filters and rules

Exclude the differences you keep on purpose, so the comparison only reports real drift.

A comparison is only useful if everything it reports deserves attention. Filters remove the differences you have decided to live with, and they can be saved per connection pair so the exceptions do not have to be re-entered every release.

Filter by object

Exclude objects by name or by wildcard. This is the usual way to ignore migration bookkeeping tables and anything generated by another tool.

Exclusion patterns
_migrationsschema_versiontmp_**_backup_2*audit_log_20??

Filter by property

Some properties differ by environment as a matter of course. Each of these can be ignored independently:

  • AUTO_INCREMENT current value — almost never meaningful between environments.
  • Routine and view DEFINER — typically a different account per environment.
  • Table and column comments.
  • Index visibility, when it is toggled for performance testing.
  • Partition definitions, when partitions are managed by a scheduled job.