[
https://issues.apache.org/jira/browse/DERBY-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3935:
-----------------------------------
Attachment: derby-3935-1b-PositionedStream.diff
Regarding Resetable and PositionedStream (PS), the former is more tightly bound
to store.
For instance, initStream handles locking, which is probably not required for
data streams outside of store. I don't see any immediate need to add the three
methods resetStream, initStream and closeStream to LOBInputStream.
I'm opting for committing what I have now, and look at combining the interfaces
later if it turns out that is the best thing to do.
I attached revision 1b, which adds two debug blocks (checking for a negative
requested position), removed the throws clause for EOFException and fixed some
errors in the JavaDoc.
After rerunning the tests, I intend to commit patch 1b.
> Introduce interface for a position aware stream
> -----------------------------------------------
>
> Key: DERBY-3935
> URL: https://issues.apache.org/jira/browse/DERBY-3935
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-3935-1a-PositionedStream.diff,
> derby-3935-1b-PositionedStream.diff
>
>
> Add an interface for streams that are aware of their position and that can
> reposition itself on request.
> Initially there will be two such stream objects; PositionedStoreStream and
> LOBInputStream.
> The interface will be used to allow the Clob implementation (including
> UTF8Reader) to handle the various internal Clob representations in a
> consistent manner when it comes to positioning the underlying byte stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
