[
https://issues.apache.org/jira/browse/DERBY-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-2806.
------------------------------------
Resolution: Fixed
Committed 'derby-2806-2a.diff' to trunk with revision 547422.
This bug is also present in 10.2, but I do not plan to back-port it to that
branch. This is due to the fact that the Clob code has been heavily rewritten
and reorganized for 10.3 and I think it might be hard to fix the bug in 10.2
without a rather large fix (my gut feeling, there might be a simple way...).
> 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.
