[
https://issues.apache.org/jira/browse/DERBY-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-2190.
-----------------------------------
Resolution: Won't Fix
Closing Won't Fix per Kristian's suggestion. Likely LOB locators and
retrieving the length with stored procedures solves this problem.
> 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
> Labels: LOB
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
