[jira] Updated: (DERBY-3970) PositionedStoreStream doesn't initialize itself properly

["Kristian Waagan (JIRA)" <ji...@apache.org>]

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

Kristian Waagan updated DERBY-3970:
-----------------------------------

    Attachment: derby-3970-1a-PositionedStoreStream_init.diff.txt

Patch 1a performs the initialization in the constructor and adjusts the calling code.
It also removed the resetting of the position variable in initStream, as only the first call will actually ensure the position of the underlying stream is set to zero. Subsequent calls are no-ops.

Patch ready for review.

> 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
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         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.