db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramin Moazeni" <rmoaz...@gmail.com>
Subject Re: Google SOC:MySQL to Derby Migration tool design question
Date Wed, 19 Jul 2006 20:14:10 GMT

I had some discussions with Satheesh on this issue. A temporary solution
for developing this tool could be to support both approaches for now by ading
an optional -DddlUtils option and if specified, DdlUtils will be used
it will be a standalone tool using Metadata and system tables approach. The tool
will support tables through ddlutils and for remaining objects, the
tool would use a shared code path that uses a combination of
DatabaseMetadata and system tables.

After development of the tool is done, we can push part of the code
that supports views, routines and CHECK constraints into ddlutils
later. After ddlutils starts supproting other database objects and
other databases, the migration tool can be modified to use the
dllutils approach only.

My goal is to finish implementation in the remaining one month.

Ramin Moazeni

On 7/13/06, Daniel John Debrunner <djd@apache.org> wrote:
> David Van Couvering wrote:
> > I'm all for helping out other projects, but IMHO Derby could really use
> > this migration tool.  We could let the DDL team know these issues exist,
> > participate in discussions with them, while at the same time scratching
> > our own itch and getting a migration tool done before Ramin disappears...
> I guess I was assuming that Derby would continue to get the tool even if
> some of the code was contributed to DDL utils, as the tool would use
> ddlutils.
> Seems Ramin is getting a good view of open source. :-)
> Options seem to be ...
>  - Add code to Derby that might be better suited to the charter of our
> sister DB project, ddlutils. Will the community reject it as outside the
> charter, or not in the best interests of Apache?
>  - Add code to ddlutils and Derby and have to deal with two communities
> and no mentor in the ddlutils project.
> I do think we should treat any submission by a Google summer of code
> student as any other contribution and not take any shortcuts, decisions
> against the charter or not in the best interest of the Apache DB project
> or Apache itself.
> One possible outcome is that Ramin completes the code, it's submitted to
> Derby attached to a Jira entty, but the portions that are ddlutils
> relevant get committed there and the derby specific code here. (Someone
> would have to drive that though).
> And hopefully the whole GoogleSoC experience is so good that Ramin
> continues to be involved in Derby and other open source projects rather
> than just "disappearing" at the end of the GoogleSoC.
> Thanks,
> Dan.

View raw message