[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Rick Hillegas updated DERBY-1651:
---------------------------------
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Moving to 10.2.3.0.
> 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.3.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
