I am all for having some sort of "synchronize" feature in addition to
"drop/create" and "reverse-engineer".
However database support of what can be done via "ALTER TABLE ..." varies
greatly by the vendor. And there is also plenty of cases that can't be
handled by the modeler at all. Some DDL changes require writing SQL
scripts manually to migrate the data intelligently, and can't be expressed
as a simple "delta" between the current state of the database and the new
state of the model. But then, having a Modeler-generated script containing
all ALTER TABLE statements can be a good start to do further manual
Actualy my personal vote would be to begin with implementing "synchronize
DataMap" for the cases when the database is updated by some external tool
or by DBA. But of course this depends on how you project process i
> If I were you, I'd go ahead and open an RFE in the issue tracker for it.
> Even if it doesn't get done immediately, I think it will get done
This would be a goo start.
This archive was generated by hypermail 2.0.0 : Sun May 02 2004 - 06:36:37 EDT