[
https://issues.apache.org/jira/browse/DERBY-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Leroux updated DERBY-4567:
----------------------------------
Attachment: DERBY-4567.sql
Hi Kim,
Thanks for documenting DERBY-4550!
The new doc appears good to me except that it doesn't explicitly cite examples
of qualified identifiers for cursors and async statements.
Those are somehow of lower interest here than for prepared statements - but
nevertheless allowed. I join a file demonstrating that point.
Please note that for now DERBY-4576 prevents the use of qualified identifiers
in GET CURSOR as demonstrated in my example. But a patch is available and that
should be fixed in the trunk soon.
- 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.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.
