[
https://issues.apache.org/jira/browse/DERBY-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-6515.
---------------------------------------
Resolution: Fixed
I decided to not backport this - it involves a change to the (tools)messages
which will remain untranslated. Also, adding the matching HoldForConnection
(added with DERBY-6585) was an improvement, not a bug, and I think documenting
this would make more sense if the HoldForConnection was also there.
derby_backport_reject_10.10
> 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
> Labels: derby_backport_reject_10_10
> Fix For: 10.11.1.1
>
> 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
(v6.3.4#6332)
