[
https://issues.apache.org/jira/browse/DERBY-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4040:
-----------------------------------
Attachment: derby-4040-2a-backport.diff
Attached the diff for the backport, 'derby-4040-2a-backport.diff'.
I had to do a manual merge, as the method InputStreamUtil.skipFully doesn't
exist on the 10.4 and 10.3 branches. Instead of using that method, I simply
chose to use InputStream.skip.
Regression tests ran successfully.
Committed to the 10.4 branch with revision 745571.
> 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.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.
