db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4002) Look at merging the interfaces PositionedStream and Resetable into one
Date Sun, 30 Jun 2013 18:18:21 GMT

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

Mamta A. Satoor updated DERBY-4002:

    Urgency: Normal
     Labels: derby_triage10_11  (was: )
> Look at merging the interfaces PositionedStream and Resetable into one
> ----------------------------------------------------------------------
>                 Key: DERBY-4002
>                 URL: https://issues.apache.org/jira/browse/DERBY-4002
>             Project: Derby
>          Issue Type: Task
>          Components: JDBC, Store
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Priority: Minor
>              Labels: derby_triage10_11
> From DERBY-3935:
> "By the way, would it make sense at some point to merge the PositionedStream interface
with Resetable? Or perhaps make PositionedStream extend Resetable? Resetable.resetStream()
is just a special case of PositionedStream.reposition(), and it seems like both PositionStoreStream
and LOBInputStream have methods that match the functionality defined by Resetable (PSS actually
implements Resetable)."
> and
> "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."
> Note that this task may also conclude that the two interfaces shouldn't be merged, but
if so the rationale should be documented under this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message