You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/05/07 19:01:30 UTC

[jira] Assigned: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

     [ https://issues.apache.org/jira/browse/DERBY-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden reassigned DERBY-1651:
-------------------------------------

    Assignee:     (was: Ramin Moazeni)

Unassigning due to inactivity.  Please reassign yourself if you would like to work on this issue.



> Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1651
>                 URL: https://issues.apache.org/jira/browse/DERBY-1651
>             Project: Derby
>          Issue Type: New Feature
>          Components: Tools
>         Environment: All platforms
>            Reporter: Ramin Moazeni
>         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.
-
You can reply to this email to add a comment to the issue online.