[DERBY-3970] PositionedStoreStream doesn't initialize itself properly

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.3.0, 10.4.2.0, 10.5.1.1
• Fix Version/s: 10.4.2.1, 10.5.1.1
• Component/s: JDBC
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 02/Dec/08 22:06
• Updated: 14/Jun/11 08:20
• Resolved: 08/Jan/09 11:27

Description

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.

Issue Links

• relates to: DERBY-3913 mismatch between error XCL30 and 22003.S.4 and parameters in usage