Ambiguity Resolver
When SchemaBank is unsure about whether a particular change would induce unwanted data loss, Ambiguity Resolver will come up and ask users for clarifications.
To illustrate, say table T has undergone the following change from version 1 to version 2.
Possible changes are
- field 'A' has been renamed to 'C' and field 'B' has been dropped
- field 'B' has been renamed to 'C' and field 'A' has been dropped
- fields 'A' and 'B' have been dropped and field 'C' has been added
Making wild guess from the possible changes may easily cause confusion when doing diff. A mistaken diff might even yield destructive SQL alter scripts that could drop the wrong column, causing data loss.
A sample screen of Ambiguity Resolver follows:
The upper window shows the two versions in tree views. The lower window shows the objects in question. Users will clarify whether a particular object from the source version should be dropped or renamed to another object found from the target version.
Regenerate Diff Reports or Alter Scripts
Everytime you generate a diff report or an alter script, it will be saved in our system so that it can be retrieved immediately next time you request it.
As the saved report and the script also contain your clarifications to ambiguity found (if any), you may sometimes want to regenerate them if you want a different resolution to the ambiguity. Clicking on the Regenerate button will do.
