Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <10533318.1200666154059.JavaMail.jira@brutus>
Date: Fri, 18 Jan 2008 06:22:34 -0800 (PST)
From: "Dyre Tjeldvoll (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3311) Client ResultSet.getHoldabilty will
 return incorrect value when the ResultSet is obtained from a procedure call
In-Reply-To: <27628831.1199900314008.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dyre Tjeldvoll updated DERBY-3311:
----------------------------------

    Derby Info:   (was: [Patch Available])

Committed revision 613169.

> Client ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3311
>                 URL: https://issues.apache.org/jira/browse/DERBY-3311
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.4.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>         Attachments: derby_3311_diff.txt
>
>
> Fixing DERBY-3305 (aka DERBY-1111) exposes that the holdability for a result set sent over DRDA is being obtained from the Statement that created the JDBC ResultSet, not its actual holdability. The two can be different when the result set is dynamic result set from a procedure.
> jdbc4.ResultSetTest.getHoldability fails in client mode.

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