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 "Ramin Moazeni (JIRA)" <de...@db.apache.org> on 2006/08/05 08:41:14 UTC
[jira] Created: (DERBY-1651) MySQL to Derby Migration Tool
MySQL to Derby Migration Tool
-----------------------------
Key: DERBY-1651
URL: http://issues.apache.org/jira/browse/DERBY-1651
Project: Derby
Issue Type: New Feature
Components: Tools
Reporter: Ramin Moazeni
Assigned To: Ramin Moazeni
Attachments: MigrationTool-MySQLtoDerby.zip
This is the first drop of MySQL to Derby Migration tool. There is currently support for tables and views.
--
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
Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate
mySQL databases to Derby. Migration tool should include both schema and data
migration options.
Posted by Daniel John Debrunner <dj...@apache.org>.
Andrew McIntyre wrote:
> On 8/21/06, Daniel John Debrunner <dj...@apache.org> wrote:
>
>>
>> That is actually engine code, so should not be used by the tools (or the
>> tests)
>
>
> Yet there are references to JVMInfo in both ij and sysinfo. Should
> these be removed, then?
Or the code moved into the common area (and bring up that whole can of
worms :-)
>
>> it would work for some cases (assuming the code was moved), but
>> it doesn't handle J2ME/CDC/Foundation or J2ME/CLDC or Java Card.
>
>
> Currently the code in JVMInfo assumes that a J2ME VM is 1.3 level, so
> the code above would currently print an error and exit on those
> platforms, would it not?
No idea, might get a class not found error in starting up. As you say
"assumes" is the key point, it assumes it's running in J2SE (or
J2ME/CDC/Foundation). It doesn't cater to the fact it might be running
in a less enabled environment so it may or may not handle that case. For
example, if Derby ran against OSGi ee.minimum I'm pretty sure it
wouldn't work and it wouldn't get a nice error message, since our error
message handling relies on classes not in OSGi ee.minimum.
Should someone fix that so that Derby produces a nice error message in
OSGi ee.minimum (or CLDC or JavaCard etc.) ? I don't see it as a
requirement.
If someone submitted a patch that made it produce a nice error message
in OSGi ee.minimum then maybe it would be committed, depends on how much
cruft code would be needed to add very little value.
In addition, the JDK_ID level produced by JVMInfo class is just designed
for J2SE and it's Derby's interpretation, not any standard Java concept.
Thus with:
JVMInfo.JDK_ID < JVMInfo.J2SE_15
who knows what JVMInfo.JDK_ID would end up being on J2ME/CLDC or
JavaCard, may end up being a value greater than JVMInfo.J2SE_15.
Dan.
Re: Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
Posted by Andrew McIntyre <mc...@gmail.com>.
On 8/21/06, Daniel John Debrunner <dj...@apache.org> wrote:
>
> That is actually engine code, so should not be used by the tools (or the
> tests)
Yet there are references to JVMInfo in both ij and sysinfo. Should
these be removed, then?
> it would work for some cases (assuming the code was moved), but
> it doesn't handle J2ME/CDC/Foundation or J2ME/CLDC or Java Card.
Currently the code in JVMInfo assumes that a J2ME VM is 1.3 level, so
the code above would currently print an error and exit on those
platforms, would it not?
andrew
Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate
mySQL databases to Derby. Migration tool should include both schema and data
migration options.
Posted by Daniel John Debrunner <dj...@apache.org>.
Andrew McIntyre wrote:
> On 8/21/06, Daniel John Debrunner <dj...@apache.org> wrote:
>
>> Andrew McIntyre wrote:
>>
>> > On 8/20/06, Satheesh Bandaram (JIRA) <de...@db.apache.org> wrote:
>> >
>> >>
>> >> 3) Looks like the code uses generics, which limit the use to JDK 1.5
>> >> platforms. While this may be ok, need to document need for JDK 1.5
>> >> platform and raise appropriate message if used in earlier platforms.
>> >> Most of derby can still run on JDK 1.3 platforms, though not required
>> >> for new indepedent modules.
>> >
>> >
>> > As well as being documented, the tool should print a useful error and
>> > then exit if a user attempts to run it on an unsupported JVM.
>>
>> I wouldn't put that as a hard requirement. You can end up with some
>> amount of hard to understand code for no benefit. Do we really need to
>> test for jdk 1.0, 1.1?, 1.2? How about J2ME/CLDC? Java Card? How about
>> J2ME/CDC without foundation profile?
>>
>> Sometimes it's cleaner and easier just to state in the documentation
>> that it requires JDK 1.5 or higher and if someone tries to run it on an
>> unsupported platform that's their issue.
>
>
> Wouldn't:
>
> if (JVMInfo.JDK_ID < JVMInfo.J2SE_15) {
> ... print error and exit ...
> }
>
> cover all of those cases and be clear as to the intention, especially
> since there's an associated error message?
That is actually engine code, so should not be used by the tools (or the
tests), it would work for some cases (assuming the code was moved), but
it doesn't handle J2ME/CDC/Foundation or J2ME/CLDC or Java Card.
If someone wants to put the effort in, fine, but I don't think it should
be any requirement to do so.
Dan.
Re: Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
Posted by Andrew McIntyre <mc...@gmail.com>.
On 8/21/06, Daniel John Debrunner <dj...@apache.org> wrote:
> Andrew McIntyre wrote:
>
> > On 8/20/06, Satheesh Bandaram (JIRA) <de...@db.apache.org> wrote:
> >
> >>
> >> 3) Looks like the code uses generics, which limit the use to JDK 1.5
> >> platforms. While this may be ok, need to document need for JDK 1.5
> >> platform and raise appropriate message if used in earlier platforms.
> >> Most of derby can still run on JDK 1.3 platforms, though not required
> >> for new indepedent modules.
> >
> >
> > As well as being documented, the tool should print a useful error and
> > then exit if a user attempts to run it on an unsupported JVM.
>
> I wouldn't put that as a hard requirement. You can end up with some
> amount of hard to understand code for no benefit. Do we really need to
> test for jdk 1.0, 1.1?, 1.2? How about J2ME/CLDC? Java Card? How about
> J2ME/CDC without foundation profile?
>
> Sometimes it's cleaner and easier just to state in the documentation
> that it requires JDK 1.5 or higher and if someone tries to run it on an
> unsupported platform that's their issue.
Wouldn't:
if (JVMInfo.JDK_ID < JVMInfo.J2SE_15) {
... print error and exit ...
}
cover all of those cases and be clear as to the intention, especially
since there's an associated error message?
andrew
Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate
mySQL databases to Derby. Migration tool should include both schema and data
migration options.
Posted by Daniel John Debrunner <dj...@apache.org>.
Andrew McIntyre wrote:
> On 8/20/06, Satheesh Bandaram (JIRA) <de...@db.apache.org> wrote:
>
>>
>> 3) Looks like the code uses generics, which limit the use to JDK 1.5
>> platforms. While this may be ok, need to document need for JDK 1.5
>> platform and raise appropriate message if used in earlier platforms.
>> Most of derby can still run on JDK 1.3 platforms, though not required
>> for new indepedent modules.
>
>
> As well as being documented, the tool should print a useful error and
> then exit if a user attempts to run it on an unsupported JVM.
I wouldn't put that as a hard requirement. You can end up with some
amount of hard to understand code for no benefit. Do we really need to
test for jdk 1.0, 1.1?, 1.2? How about J2ME/CLDC? Java Card? How about
J2ME/CDC without foundation profile?
Sometimes it's cleaner and easier just to state in the documentation
that it requires JDK 1.5 or higher and if someone tries to run it on an
unsupported platform that's their issue.
Dan.
Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
Posted by Andrew McIntyre <mc...@gmail.com>.
On 8/20/06, Satheesh Bandaram (JIRA) <de...@db.apache.org> wrote:
>
> 3) Looks like the code uses generics, which limit the use to JDK 1.5 platforms. While this may be ok, need to document need for JDK 1.5 platform and raise appropriate message if used in earlier platforms. Most of derby can still run on JDK 1.3 platforms, though not required for new indepedent modules.
As well as being documented, the tool should print a useful error and
then exit if a user attempts to run it on an unsupported JVM.
andrew
[jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=comments#action_12429249 ]
Satheesh Bandaram commented on DERBY-1651:
------------------------------------------
Some general comments:
1) I think a design document to explain what each class does and how they interact with each other is required. Other option is to create a package.html file and document design/code in place. I think the second option is better.
At the mininum, each class needs a detailed javadoc at the beginning and for each major method. Important and useful contribution like this may not get accepted if not documented properly.
2) Package location needs to be changed. All tools are in org.apache.derby.tools package. Best to follow existing tools like IJ, DBLOOK model so it would be easy to use and to enable derbyrun option for this tool later.
3) Looks like the code uses generics, which limit the use to JDK 1.5 platforms. While this may be ok, need to document need for JDK 1.5 platform and raise appropriate message if used in earlier platforms. Most of derby can still run on JDK 1.3 platforms, though not required for new indepedent modules.
4) There are many areas that need improvements in the code... like exception handling, importing only classes that are needed not the whole package, deleting code that is in comments etc. I understand the code is still in development.
I would like to suggest you focus on completing current functionality very well, document what you have done, move code and integrate it at appropriate location and test current functionality before adding more.
Better to submit partial code that is well written than submit more code that is not very usable.
> 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
[jira] Commented: (DERBY-1651) MySQL to Derby Migration Tool
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=comments#action_12425938 ]
Satheesh Bandaram commented on DERBY-1651:
------------------------------------------
Ramin, I am going to update the description and summary. If you don't like it, please change it as you see fit.
It is important to have the description cover the whole feature but say you are working on implementing parts of the functionality and submit each part as being developed.
> MySQL to Derby Migration Tool
> -----------------------------
>
> Key: DERBY-1651
> URL: http://issues.apache.org/jira/browse/DERBY-1651
> Project: Derby
> Issue Type: New Feature
> Components: Tools
> Reporter: Ramin Moazeni
> Assigned To: Ramin Moazeni
> Attachments: MigrationTool-MySQLtoDerby.zip
>
>
> This is the first drop of MySQL to Derby Migration tool. There is currently support for tables and views.
--
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
[jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Ramin Moazeni (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=comments#action_12428140 ]
Ramin Moazeni commented on DERBY-1651:
--------------------------------------
[8/15/06]
This revision added support for procedures, and catalogs to the Database Migration toolkit as well as the User Interface. Currently, migration of tables, views, and catalogs is suported as well as assistance with migration of stored procedures. The patch is attched with this report.
> 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.0.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
Re: [jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by Jørgen Løland <Jo...@Sun.COM>.
Andrew McIntyre (JIRA) wrote:
> [ 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.
>
Just a thought... wouldn't VTIs be perfect for this purpose?
--
Jørgen Løland
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Ramin Moazeni (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Ramin Moazeni updated DERBY-1651:
---------------------------------
Attachment: DBMigration.diff
> 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.0.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
[jira] Assigned: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Rick Hillegas updated DERBY-1651:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.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.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
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Andrew McIntyre updated DERBY-1651:
-----------------------------------
Derby Info: [Patch Available]
> 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
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Satheesh Bandaram updated DERBY-1651:
-------------------------------------
Summary: Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options. (was: MySQL to Derby Migration Tool)
Environment: All platforms
Fix Version/s: 10.2.0.0
Description:
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.
was:This is the first drop of MySQL to Derby Migration tool. There is currently support for tables and views.
> 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.0.0
>
> Attachments: 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
[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL
databases to Derby. Migration tool should include both schema and data
migration options.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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