[
https://issues.apache.org/jira/browse/DERBY-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Leroux updated DERBY-4550:
----------------------------------
Attachment: DERBY-4550_4.sql
DERBY-4550_4.patch
Attaching a new patch for this issue.
Currently, Session objects hold reference for prepared statements,
cursors/cursor statements and asynchronous statements.
All now accept the '@' notation to design an identifier outside of the current
connection. See the attached SQL file for example.
Add some tests to ij7.sql.
Changed a test result in ij2.out to reflect the fact that error messages now
provides the session name as well as the faulty statement:
ij> Connect 'jdbc:derby:memory:dummy;create=true';
ij> EXECUTE stmt;
IJ ERROR: Unable to establish prepared statement s...@connection0
Pass derbytool and ToolScript test suites.
Ready for review.
> 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
>
>
> 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.
