[
https://issues.apache.org/jira/browse/DERBY-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835859#action_12835859
]
Rick Hillegas commented on DERBY-4550:
--------------------------------------
Hi Sylvain,
I agree that having two kinds of dot-separated names is confusing. I was only
suggesting that we use qualified identifiers for connection-scoped variables.
So in the example which you just gave...
DESCRIBE C.T;
...I agree with you that the meaning should continue to be "the table T in the
schema C of the database of the current connection".
Maybe we shouldn't use PERIOD to separate the two parts of a qualified
identifier. It may give rise to too much confusion. Maybe the separator should
be some other character which can't appear in an identifier, like @. If we use
@ we might want to flip the order
variableName @ connectionName
What do you think?
> 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
>
>
> 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.
