You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/05/28 00:02:03 UTC

[jira] [Updated] (DERBY-6585) add HoldForConnection ij command to match NoHoldForConnection

     [ https://issues.apache.org/jira/browse/DERBY-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-6585:
--------------------------------------

    Attachment: DERBY-6585_doc.diff
                DERBY-6585_src.diff

Attaching a doc and src tree patch which adds the HoldForConnection ij command to match NoHoldForConnection.

The source patch also adds a little ij test which shows the behavior of these two commands.

> add HoldForConnection ij command to match NoHoldForConnection
> -------------------------------------------------------------
>
>                 Key: DERBY-6585
>                 URL: https://issues.apache.org/jira/browse/DERBY-6585
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 10.11.0.0
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-6585_doc.diff, DERBY-6585_src.diff
>
>
> DERBY-6515 was created to document the NoHoldForConnection ij command, which was used in some of Derby's sql style tests.
> In subsequent comments, it was felt there should be a matching HoldForConnection ij command to set the value back to the default (ResultSet.HOLD_CURSORS_OVER_COMMIT).



--
This message was sent by Atlassian JIRA
(v6.2#6252)