[
https://issues.apache.org/jira/browse/DERBY-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-4040.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.2.1
10.3.3.1
Backported the fix from 10.4 to the 10.3 branch with revision 745811.
The tinderbox test for 10.4 ran cleanly.
I'm resolving the issue, and will await the tinderbox results from 10.3 before
I close.
> SQLChar.getLength returns wrong length for some data values
> -----------------------------------------------------------
>
> Key: DERBY-4040
> URL: https://issues.apache.org/jira/browse/DERBY-4040
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.3.1, 10.4.2.0, 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.3.3.1, 10.4.2.1, 10.5.0.0
>
> Attachments: derby-4040-1a-SQLChar_length_and_test.diff,
> derby-4040-1a-SQLChar_length_and_test.stat, derby-4040-2a-backport.diff
>
>
> SQLChar.getLength() returns the wrong length of the data value in some cases.
> For the bug to be triggered, the value must contain characters that are
> represented by two or three bytes, and Derby must store the value as a stream.
> In my ad-hoc testing, I found that a value of length 10886 with CJK
> characters doesn't trigger the bug, but 10887 does trigger the bug. Further,
> for a range of lengths the bug can also been observed for CLOB columns (when
> doing 'select length(clobcolumn)').
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
