[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Mike Matrigali updated DERBY-1651:
----------------------------------
Derby Info: (was: [Patch Available])
Unsetting patch available, derby is using the patch available flag as an
indication that the current patch is ready to
be reviewed/committed. The patch has been reviewed by a couple of committers
and there are a number of comments in the issue indicating this patch is not
ready to be
committed. If the contributer disagrees go ahead an set patch available
again, and respond to the comments posted.
> Develop a mechanism to migrate mySQL databases to Derby. Migration tool
> should include both schema and data migration options.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1651
> URL: http://issues.apache.org/jira/browse/DERBY-1651
> Project: Derby
> Issue Type: New Feature
> Components: Tools
> Environment: All platforms
> Reporter: Ramin Moazeni
> Assigned To: Ramin Moazeni
> Fix For: 10.2.2.0
>
> Attachments: DBMigration.diff, MigrationTool-MySQLtoDerby.zip
>
>
> Develop a mechanism to migration databases created by other database engines
> to Derby. While my current interest is to migrate mySQL databases to Derby,
> the tool could be developed in a way to extend this mechanism to allow
> migration from other database engines in the future.
> More details of proposed functionality and implementation strategy can be
> found at:
> http://wiki.apache.org/db-derby/MysqlDerbyMigration
> The plan is to develop and submit patches incrementally. First patch supports
> migration of tables and views from mySQL database to Derby.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
