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-6515) ij doesn't list its command NoHoldForConnection in the help menu
Date Wed, 21 May 2014 13:44:38 GMT

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

Kim Haase commented on DERBY-6515:

Thanks for doing the docs, Myrna! The topic looks good. I am a bit confused, though, because
the discussions of holdability in the Developer's Guide say that holdability is the default,
not NOHOLDABILITY. Did you mean to say something like 

"Sets the default holdability for a connection to NOHOLDABILITY (that is, to ResultSet.CLOSE_CURSORS_AT_COMMIT).
By default, result sets are held open on commit. See "Scrollable result sets" in the Derby
Developer's Guide for more information."

Is there an ij command to change the default back to holdability?

> ij doesn't list its command NoHoldForConnection in the help menu
> ----------------------------------------------------------------
>                 Key: DERBY-6515
>                 URL: https://issues.apache.org/jira/browse/DERBY-6515
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>         Attachments: DERBY-6515_src.diff, DERBY_6515_doc.diff
> ij has a command to set the default holdability for a connection:
> Connection#setHoldability(ResultSet.CLOSE_CURSORS_AT_COMMIT)
> called "noholdforconnection". I think it should be documented and included in the inline
help menu.

This message was sent by Atlassian JIRA

View raw message