[jira] Updated: (DERBY-2890) Simplify handling of maxPos in UpdatableBlobStream and ClobUpdatableReader

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen updated DERBY-2890:
--------------------------------------

    Attachment: maxpos.stat
                maxpos.diff

Attaching patch which uses Long.MAX_VALUE instead of -1 to indicate no limit on the stream length. All tests passed.

> 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: 10.4.0.0
>            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.