db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3755) ij's help text lacks the optional [HOLD | NOHOLD] syntax for GET CURSOR
Date Thu, 03 Jul 2008 17:13:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610282#action_12610282

Kim Haase commented on DERBY-3755:

Actually, there's a mismatch between the help command's version of the syntax and that in
the tools guide topic for GET CURSOR. The tools guide topic (http://db.apache.org/derby/docs/dev/tools/rtoolsijcomref36618.html)
does not mention SCROLL INSENSITIVE. It also indicates that HOLD or NOHOLD must be preceded
by WITH:

GET [ WITH { HOLD | NOHOLD } ] CURSOR Identifier AS String

Looks as if [SCROLL INSENSITIVE] should be added to the doc topic, and [ WITH { HOLD | NOHOLD
} ]  should be added to the help. 

Perhaps [SCROLL INSENSITIVE] was left out of the doc because it is the default and there is
no other choice, but we should indicate that a SQL statement that uses that syntax is valid.
I can file a separate issue for this.

> ij's help text lacks the optional [HOLD | NOHOLD] syntax for GET CURSOR
> -----------------------------------------------------------------------
>                 Key: DERBY-3755
>                 URL: https://issues.apache.org/jira/browse/DERBY-3755
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>             Fix For:
> ij's help command shows the syntax of GET CURSOR as:
>                                -- gets a cursor (JDBC result set) on the query
>                                -- SCROLL cursors are only available 
>                                -- in JDBC 2.0 and higher. 
>                                -- (Cursor scroll type is ignored in JDBC 1.X.) 
> One can actually also specify holdability, so the syntax show read:
> and the comment should also state that HOLD is the default.

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

View raw message