db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2890) Simplify handling of maxPos in UpdatableBlobStream and ClobUpdatableReader
Date Wed, 04 Jul 2007 08:21:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510107

Knut Anders Hatlen commented on DERBY-2890:

Merged to 10.3 to resolve conflict with DERBY-2891. Committed revision 553121.

> Simplify handling of maxPos in UpdatableBlobStream and ClobUpdatableReader
> --------------------------------------------------------------------------
>                 Key: DERBY-2890
>                 URL: https://issues.apache.org/jira/browse/DERBY-2890
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>         Attachments: maxpos.diff, maxpos.stat
> UpdatableBlobStream and ClobUpdatableReader have a maxPos field which tells when to stop
reading the underlying stream regardless of whether or not end-of-stream has been reached.
If there is no limit, maxPos is set to -1. If we instead set maxPos to infinity (Long.MAX_VALUE
is close enough), the special handling of maxPos==-1 could be removed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message