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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/07/16 17:28:04 UTC
[jira] Updated: (DERBY-2941) With 10.2, Closing a resultset after
retrieving a large > 32665 bytes value with Network Server does not release
locks
[ https://issues.apache.org/jira/browse/DERBY-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-2941:
----------------------------------
Attachment: DERBY-2941_diff.txt
Attaching a patch for this issue. Patch only differs from patch attached to DERBY-2892 in that it has some corrections to javadoc.
-Changes EXTDTAInputStream to use ResultSet.getCharacterStream, ResultSet.getBinaryStream instead of getClob(), getBlob..
- Alters EngineResult for getLenth(int columnIndex) and isNull(int columnIndex) methods
-Enables LargeDataLocksTest
derbyall passed with only known failures.
I would most appreciate review. If I hear no objections I will commit tomorrow.
> With 10.2, Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2941
> URL: https://issues.apache.org/jira/browse/DERBY-2941
> Project: Derby
> Issue Type: Sub-task
> Components: Network Server
> Affects Versions: 10.2.2.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Fix For: 10.2.2.1
>
> Attachments: DERBY-2941_diff.txt
>
>
> Making a subtask for the 10.2 fix for this issue as the fix for 10.3 will be different.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.