This content has been marked as final. Show 5 replies
If one View refers to another View, the Views should normally appear in the appropriate order in the DDL generated by Data Modeler.
However it appears that this is not happening in your case?
Is there anything unusual about your view definitions?
What version of Data Modeler are you using?
my Datamodeler version is 220.127.116.114.
In a simple test with 1 table and 3 cascading views it worked for an Oracle generation, but I use SQLServer and SQLServer (2000 and 2005) DDL generation uses alphabetical order of view names.
It is the same with the new 18.104.22.1684 version.
On the other hand some of the SQLServer views loaded into the model from data dictionary are too complex to be opened by the query editor, so dependencies may not be recognized.
So I hoped a manual hint would be possible.
I'm afraid the reordering is only done when generating for Oracle.
Unfortunately there's no way to influence the order when generating for other types of database.
I've logged an enhancement request on this.
I'm experiencing the same issue with a "Oracle Database 11g" Physical Model.
"CREATE OR REPLACE VIEW" in the script are in alphabetical order.
I'm on 22.214.171.1240 under Win7 and Java 1.6.0_38.
When generating for Oracle Database 11g, the relevant views should normally be reordered when one view is dependent on another.
However this reordering is not always done. We are hoping to fix this in the next release.