Diff between objects in different named default schemas doesn't see them as the same object
Description
Environment
Diff
Activity
Show:
Nathan Voxland May 27, 2014 at 2:17 PM
Able to recognize defaults schema as the same across connections. Different alternate schemas need to be matched up with a custom SchemaComparator
When you are doing a diff between two databases with different names for their default schema, tables named the same are seen as different objects for comparison because of the differences in schema name.
This causes diff and diffChangeLog to generate "missing" and "unexpected" details for the tables, rather than a "changed" comparision.