db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3311) Client ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call
Date Wed, 09 Jan 2008 18:35:34 GMT

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

Daniel John Debrunner updated DERBY-3311:
-----------------------------------------

    Attachment: derby_3311_diff.txt

Patch to change the DRDA code to obtain the holdability explicitly from the result set or
statement as required as a result set may have a different holdability to its statement.

> 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.


Mime
View raw message