[
https://issues.apache.org/jira/browse/DERBY-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871182#action_12871182
]
Kristian Waagan commented on DERBY-2190:
----------------------------------------
Did the locator implementation remove this problem?
I ran the derbynet/SuicideOfStreamingTest, but it failed on trunk. It passed
when I used an old derbyclient.jar (10.2), which didn't have locator support.
It seems the test isn't part of any suite. The test forces an error when
streaming the data from the server to the client, and the failure is simply
caused by the fact that the piece of code that throws the exception is no
longer being run. Instead the data is transferred using the LOB stored
procedures.
Unless I get any push-back, I plan to resolve this issue as "Won't Fix".
> Make it possible to retrieve length information from LOB created without
> length information after whole LOB was streamed
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2190
> URL: https://issues.apache.org/jira/browse/DERBY-2190
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Reporter: Tomohito Nakayama
> Priority: Minor
>
> DERBY-1471 made it impossilble to get length information from LOB created
> without length information, as exception of XJ216.S.
> This is due to improvement in DERBY-1471 that it was escaped to expand entire
> LOB into memory and expected behavior.
> However, after whole of LOB was streamed, it is possible to know length of
> the LOB and
> throw exception in that case is too strict .
> This issue make it possible to get length information from LOB after whole
> LOB was streamed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
