[
https://issues.apache.org/jira/browse/DERBY-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3970:
-----------------------------------
Derby Info: (was: [Patch Available])
Affects Version/s: 10.5.0.0
Fix Version/s: 10.5.0.0
Tests ran without errors (derbyall, suites.All).
Committed patch 1a to trunk with revision 722812.
> PositionedStoreStream doesn't initialize itself properly
> --------------------------------------------------------
>
> Key: DERBY-3970
> URL: https://issues.apache.org/jira/browse/DERBY-3970
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.3.0, 10.4.2.0, 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-3970-1a-PositionedStoreStream_init.diff.txt
>
>
> When a PositionedStoreStream is created on top of a stream from store, it
> must properly initialize itself.
> Proper initialization consists of initializing and resetting the stream to
> make sure the states of the streams are in sync.
> A case of out of sync stream states was detected in a test where the Clob
> reference wasn't kept, but a new Clob object was created for each operation,
> i.e:
> rs.getClob(1).length();
> rs.getClob(1).getSubString(...);
> A symptom of out of sync stream states is EOFException on a valid request.
> I don't think the access style above is supposed to work, but the proper
> initialization should be performed anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
