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 Thu, 13 Jul 2006 16:33:57 GMT
Daniel John Debrunner wrote:
> Satheesh Bandaram wrote: 
>>Jean T. Anderson wrote:
>>>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 ).
>>This is important... While ddlUtils goal is to support all databases,
>>Ramin is attempting to fix his target database to Derby and to make
>>source database mySQL for his migration utility. (for now) It doesn't
>>seem like Ramin should take on adding database specific code to ddlUtils
>>(that DatabaseMetadata might not expose directly) and to test on 13
>>databases that ddlUtils currently supports.
> Isn't the point of Google summer of code to introduce students to open
> source development, and this switch to ddlutils and additonal community
> involvement is typical of open source? Scratch your own itch but also
> benefit the community as well.

It's also possible DdlUtils might welcome partial contributions (and
that other hands might dive in to fill in other databases). For anyone
interested, a DdlUtils discussion thread started at:


and here's the tiny url:


View raw message