[
https://issues.apache.org/jira/browse/DERBY-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838046#action_12838046
]
Rick Hillegas commented on DERBY-4550:
--------------------------------------
Thanks for the revised patch, Sylvain. The tests ran cleanly for me except for
discrepancies in DerbyNet/holdCursorIJ and DerbyNetClient/holdCursorIJ. I
updated the canons for those tests. There was also an error in
OnlineCompressTest, which I thought was an instability in that test: it didn't
seem related to your work and the error did not recur when I ran the test
standalone. Committed at subversion revision 916014.
Thanks for this great feature. I will add a doc issue so that we don't forget
to update the ij documentation accordingly.
> Using ij to copy data from one DB to an other
> ---------------------------------------------
>
> Key: DERBY-4550
> URL: https://issues.apache.org/jira/browse/DERBY-4550
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Reporter: Sylvain Leroux
> Assignee: Sylvain Leroux
> Priority: Minor
> Attachments: DERBY-4550.diff, DERBY-4550.sql, DERBY-4550_2.diff,
> DERBY-4550_2.sql, DERBY-4550_3.patch, DERBY-4550_3.sql, DERBY-4550_4.patch,
> DERBY-4550_4.sql, DERBY-4550_5.patch, DERBY-4550_6.patch
>
>
> It is possible to have open connections to several databases while running
> ij, but it is not currently possible to copy data from one DB to an other one.
> Not only such a feature would allow to copy data between Derby databases.
> But, ij being mostly DB agnostic, if will ease import/export from any JDBC
> compliant data source.
> See
> http://old.nabble.com/Using-IJ-to-copy-data-from-one-DB-to-an-other-one-td27598138.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
