From: "M.Francis" <[EMAIL PROTECTED]> > fyi, Erwin does allow this to be 'automated.' > With user interaction the metadata in your erd is compared to that of the > target database. > When you perform a change in your erd and wish to forward engineer it > to your database the tool determines the does a complete comparison with > existing metadata to that of your erd or selected objects you chose to implement.
If the erd in ERwin contains triggers and stored procedures, then it can be automated to a large extent. But ERwin can only generate a script of the necessary ddl. A modification could very well need some dml. Consider the case of adding a column and the column is set to NOT NULL. Before the contraints for the table are re-enabled, the column must be populated with data. It may be a simple matter to manually insert the necessary code into the generated script, but this just shows the impossibility of ever *fully* automating the creation of the complete script. > As per the example used above... > New column as well as its dependencies whether in other tables/constraints/triggers etc. are handled, and generated in an RDBMS engine specific script such that the sequence is correct (i.e. renaming the table creating a new table and > adding the constraint etc.) and can be applied... Yes, *if* the stored code (triggers and stored procedures) are part of the erd and can be included in the generated script. Otherwise they have to be inserted manually. > The only drawback is that it leaves the old metadata and you have to do > a clean up of the same.. If this was the only drawback, I would consider it a complete success. Tomm -- "Very funny, Scotty... now beam down my clothes!" ____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________
