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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2008/01/09 18:38:34 UTC
[jira] Created: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
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
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.
[jira] Updated: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner updated DERBY-3311:
-----------------------------------------
Derby Info: [Patch Available]
Patch fixes the test, jdbc4._Suite passes as well as jdbcapi.HoldabilityTest and lang.HoldCursorTest.
> 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.
[jira] Commented: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559039#action_12559039 ]
Dyre Tjeldvoll commented on DERBY-3311:
---------------------------------------
All tests pass with this patch for me. +1 to commit.
> 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.
[jira] Closed: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner closed DERBY-3311.
----------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.0.0
Fixed in trunk.
> 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
> Fix For: 10.4.0.0
>
> 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.
[jira] Updated: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561180#action_12561180 ]
Myrna van Lunteren commented on DERBY-3311:
-------------------------------------------
Can this now be closed?
> 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.
[jira] Updated: (DERBY-3311) Client ResultSet.getHoldabilty will
return incorrect value when the ResultSet is obtained from a procedure call
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ 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.