[ http://issues.apache.org/jira/browse/DERBY-1651?page=comments#action_12429214 ] Daniel John Debrunner commented on DERBY-1651: ----------------------------------------------
The patch has classes in the package 'Derby", I assume these would need to move into something in the org.apache.derby.tools area. The new files have the old coopyright/licence header so would need to be fixe dup to match the current style. The code has hardly any comments, this stopped me from reviewing it any more as I don't have time to guess or try to figure out what each class and method is meant to be doing. > 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.1.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
