[
https://issues.apache.org/jira/browse/DERBY-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2806:
-----------------------------------
Attachment: derby-2806-2a.stat
derby-2806-2a.diff
'derby-2806-2a.diff' implements the required changes and adds a test case that
demonstrates the bug/problem.
Changes from the previous patch:
* Instead of returning/creating the PositionedStoreStream in SQLClob, it is
done in StoreStreamClob.
This is better since it isolates the change more.
* PositionedStoreStream no longer handle the encoded length. This was too
specific, and should be handled in the next higher level instead. This allows
it to be used for both Clob and Blob.
* Removed some unrelated, though valid, changes regarding error reporting. I
hope to address them in a separate Jira.
Ran suites.All/derbyall without failures.
> 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, derby-2806-2a.diff,
> derby-2806-2a.stat, 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.
