[
https://issues.apache.org/jira/browse/DERBY-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834349#action_12834349
]
Sylvain Leroux commented on DERBY-4550:
---------------------------------------
Thanks for your comments Rick.
Using a level on indirection to reference identifiers created by another
connection will definitively be more readable from an user point of view. I
will work on that direction.
As you propose, I think it would be a good starting point to state that other
connection's namespace are "read only". New prepared statements (or maybe
cursors or even other objects?), could only be added to the current connection
namespace.
So that fragment would be invalid:
ij> set connection fred_conn;
ij> prepare alice_conn.second_select as 'select * from t1';
But what about:
ij> set connection fred_conn;
ij> prepare fred_conn.second_select as 'select * from t1';
One option would be to only allow unqualified identifiers when introducing a
/new/ identifier. And only using qualified identifiers for referencing
/existing/ identifiers.
> 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
>
>
> 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.
