db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6515) ij doesn't list its command NoHoldForConnection in the help menu
Date Fri, 23 May 2014 16:26:02 GMT

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

Dag H. Wanvik commented on DERBY-6515:

I agree there should be a symmetrical HoldForConnection command as well; the NoHoldForConnection
was probably added for some testing and as such it was good enough; one could always start
another connection. For a general purpose tool, though, it looks like a careless omission.

> 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
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For:
>         Attachments: DERBY-6515_src.diff, DERBY-6515_src.diff2, DERBY_61515_doc.diff2,
DERBY_6515_doc.diff, index.html, rtoolsijcomrefnohold.html
> 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