diff generates add/drop for foreign keys that already exist in both db's


I suspect this is a bug, but diff appears to produce changesets for foreign keys that are actually the same. Example below. Is this something that is on the radar to be fixed?



It is a known issue currently.  The trouble is that the JDBC drivers vary significantly in how they return metadata on foreign keys and indexes and how well you can tell them apart, especially if you have multiple columns in a constraint.

For now you’ll just have to clean up the diff result to fix any inconsistencies (which you should do anyway, because the output of any database diff will usually be different than what you want in one way or another)