db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Leroux (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4567) Update the Tools documentation to describe the qualified identifiers which Sylvain just added to ij
Date Thu, 11 Mar 2010 10:54:28 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844011#action_12844011
] 

Sylvain Leroux commented on DERBY-4567:
---------------------------------------

Hi Kim,

This is great to me now. Except one minor thing:
In out/tools/rtoolsijcomref37862.html, the text says "; it must not be the same as any other
identifier for an async statement on the *current* connection".
But, if a connection name is explicitly given using the @ notation, the identifier must not
already be in use for an async statement in the /designated/ connection - however it is allowed
to exists in the /current/ connection (if the current connection is not the same as the designated
connection of course).


Thanks again for working on this!
- Sylvain

> Update the Tools documentation to describe the qualified identifiers which Sylvain just
added to ij
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4567
>                 URL: https://issues.apache.org/jira/browse/DERBY-4567
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 10.6.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-4567-2.diff, DERBY-4567-2.stat, DERBY-4567-2.zip, DERBY-4567.diff,
DERBY-4567.sql, DERBY-4567.stat, DERBY-4567.zip
>
>
> See DERBY-4550. The ij tool now supports qualified identifiers. Previously only one-part
names were allowed for the identifiers bound to prepared statements and cursors. Now those
identifiers can have two parts:
>   identifier @ connectionName

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message