If this is the simplest approach in terms of design and code re-use it
sounds good to me, *as long as* the user doesn't have this split exposed
to him/her, and instead sees one seamless tool and user experience.
In particular, if Things Go Wrong, what is the user flow/experience --
how does the user back things out, figure out what went wrong, etc.
Does this approach complicate error determination and recovery?
Thanks,
David
Ramin Moazeni wrote:
Hello
As per my earlier post regarding the design document for MySQL to
Derby Migration tool located at
http://wiki.apache.org/db-derby/MysqlDerbyMigration/DesignDocument, I
proposed two approches: 1) based on the use of DatabaseMetaData and 2)
using DdlUtils tool.
The DdlUtils tool seems not be capable of migrating views, CHECK
constraints, and stored procedures. I would like to know what do you
think if DdlUtils tool can be reused for migrating the tables and
Indexes, and use the DatabaseMetadata for migrating views and stored
procedures? .....
Your comments are appreciated.....
Thanks
Ramin Moazeni
