Unable to Reverse Engineer and Model Unique Indexes.
Reverse Engineering and the Model to database comparisons both did not “deal” with the existing Unique Indexes that were the same as the PK constraints. The unique indexes were not RE’d into the Model even though they existed in the database.
Unique property of Indexes that were automatically created in the database when a Primary Key was created are not Reversed Engineered.
Indexes for Primary and Unique Key Constraints option should work is shown below (however, due to the defect, it currently does not work that way).
- when enabled - Indexes of Primary and Unique Keys are reversed engineered, their properties included (eg. Unique)
- when disabled - Indexes of Primary and Unique Keys are not reversed engineered at all
Waiting for fix in a future release of Toad Data Modeler.