db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2763) In the Network Client InputStreams and Readers returned from LOB's should be sensitive to underlying LOB data changes.
Date Mon, 18 Jun 2007 18:38:26 GMT

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

A B commented on DERBY-2763:
----------------------------

Noticed that the changes for this issue are causing some javadoc warnings:

[javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveBlobLocatorInputStream.java:53:
warning - @param argument "connection" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveBlobLocatorInputStream.java:74:
warning - @param argument "connection" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveClobLocatorInputStream.java:53:
warning - @param argument "connection" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveClobLocatorReader.java:72:
warning - @param argument "connection" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveClobLocatorReader.java:72:
warning - @param argument "r" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveClobLocatorReader.java:110:
warning - @param argument "connection" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveClobLocatorReader.java:110:
warning - @param argument "r" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveLOBLocatorInputStream.java:87:
warning - @param argument "connection" is not a parameter name.
      [javadoc] java\client\org\apache\derby\client\am\UpdateSensitiveLOBLocatorInputStream.java:123:
warning - @param argument "connection" is not a parameter name.

> In the Network Client InputStreams and Readers returned from LOB's should be sensitive
to underlying LOB data changes.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2763
>                 URL: https://issues.apache.org/jira/browse/DERBY-2763
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.3.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>             Fix For: 10.3.0.0
>
>         Attachments: Approach_2.diff, Approach_2.stat, Approach_2.txt, Approach_3.diff,
Approach_3.stat, Approach_4.diff, Approach_4.stat, LOBLengthPersists.java, UpdateSensitiveStreamsForClient_v1.diff,
UpdateSensitiveStreamsForClient_v1.stat, UpdateSensitiveStreamsForClient_v2.diff, UpdateSensitiveStreamsForClient_v2.stat,
UpdateSensitiveStreamsForClient_v3.diff, UpdateSensitiveStreamsForClient_v3.stat, UpdateSensitiveStreamsForClient_v4.diff,
UpdateSensitiveStreamsForClient_v4.stat
>
>
> Currently the Embedded and Network Client would differ 
> in behaviour when the following series of steps is 
> followed.
> a) Create an empty Blob
> b) get an InputStream using Blob.getBinaryStream()
> c) write data into this Blob
>    c.1) Get an OutputStream
>    c.2) Use OutputStream.write(byte [] b) to write
>         into this Blob.
> d) Now read from the InputStream obtained in step b)
>    and print the number of bytes read as output.
> The output of step d) differs in the client and in the Embedded side.
> In the Client
> -------------
> The number of bytes read would always be -1.
> In the Embedded
> ---------------
> The number of bytes would be the number of bytes we
> reflected.
> The above behaviour in the NetworkClient is because
> the length of the Blob is read once and stored in the 
> constructor of the locator Stream returned (in the 
> attribute maxPos).
> This instead should be read each time we use the streams.
> A similar issue exists for Clobs also.
> I will raise a seperate JIRA issue for this.

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


Mime
View raw message