db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: Google SOC:MySQL to Derby Migration tool design question
Date Wed, 12 Jul 2006 20:49:22 GMT
Jean T. Anderson wrote:
> Ramin Moazeni wrote:
>>Hi Bryan,
>>I am not sure this would be feasible given the amount of time I have
>>to finish this project as well as my familiarity with DdlUtils code
>>base. But if everybody agrees to it, I can start working on it.
> One thing to consider is DdlUtils is database agnostic. For example,
> adding support for "create view" doesn't mean just adding it for Derby,
> but also adding it for every database supported (see the list at
> http://db.apache.org/ddlutils/database-support.html ).
> You might consider posting to ddlutils-dev@db.apache.org to ask what
> level of effort people think might be required to implement the missing
> features.

Some discussion regarding constraints, triggers, and stored procedures
is here:



>  -jean
>>On 7/11/06, Bryan Pendleton <bpendleton@amberpoint.com> wrote:
>>>>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? .....
>>>Perhaps another possibility would be for you to improve DdlUtils so
>>>that it has these desirable features. The end result would be a better
>>>DdlUtils *and* a MySQL-to-Derby migration tool.

View raw message