You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I manage a large database made of 83 tables.
It is virtually impossible to work with a complete ERDesigner model of that database.
Envisaged workaround: Build several fraction model each covering a certain aspect of the whole database.
When I reverse engineer a fraction of the complete model for the first time, everything is o.k.
But the first time the DOMAINs I use are reverse engineered, and when I try to add more table to the same model fraction, ERDesigner complains about the DOMAINs already existing.
Possible solution:
Add an option "Ignore duplicate DOMAINs" to the "Reverse engineer" function.
This would be a very valuable enhancement to ERDesigner allowing to model & manage even very large databases.
The text was updated successfully, but these errors were encountered:
I manage a large database made of 83 tables.
It is virtually impossible to work with a complete ERDesigner model of that database.
Envisaged workaround: Build several fraction model each covering a certain aspect of the whole database.
When I reverse engineer a fraction of the complete model for the first time, everything is o.k.
But the first time the DOMAINs I use are reverse engineered, and when I try to add more table to the same model fraction, ERDesigner complains about the DOMAINs already existing.
Possible solution:
Add an option "Ignore duplicate DOMAINs" to the "Reverse engineer" function.
This would be a very valuable enhancement to ERDesigner allowing to model & manage even very large databases.
The text was updated successfully, but these errors were encountered: