[
https://issues.apache.org/jira/browse/DERBY-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504934
]
Kristian Waagan commented on DERBY-2806:
----------------------------------------
I wasn't able to get the repro to fail, and it was a bit hard to understand
from the output if it did fail or not.
Maybe some other patch has changed the behavior.
In my next patch I will add a new test called
ClobUpdateableReader.testMultiplexedOperationProblem, which does still fail
without the patch. It only tests if Clob experiences the bug.
> calling getByteLength on org.apache.derby.impl.jdbc.StoreStreamClob makes
> BinaryStream, fetched before this call, unusable
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2806
> URL: https://issues.apache.org/jira/browse/DERBY-2806
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.2.0, 10.3.0.0
> Reporter: Anurag Shekhar
> Assignee: Kristian Waagan
> Fix For: 10.3.0.0
>
> Attachments: derby-2806-1a.diff, Derby2806.java
>
>
> StoreStreamClob.getByteLength first resets the internal stream and then reads
> the entire stream. Due to this any read on Stream obtained by
> StoreStreamClob.getRawByteStream returns -1.
> StoreStreamClob is a read only InternalClob, so probably keeping the length
> in a variable will be good idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
