db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
Date Thu, 13 Dec 2007 08:58:43 GMT

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

Andrew McIntyre updated DERBY-1651:
-----------------------------------

    Fix Version/s:     (was: 10.2.3.0)

Unsetting fix version, no movement for over a year.

> 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
>            Assignee: 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.


Mime
View raw message