[
https://issues.apache.org/jira/browse/DERBY-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500304
]
Anurag Shekhar commented on DERBY-2694:
---------------------------------------
I think my comments in this issue has been little confusing.
The patch I have submitted fix of the bug which was corrupting last char while
returning from a function. Apart from this issue I have also mentioned another
issue in my comments which causes the a large string (containing multibyte
chars). These are two different issue. My patch fixes the first issue alone.
> org.apache.derby.impl.drda.DDMWriter uses wrong algorithm to avoid spliting
> varchar in the middle of a multibyte char.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2694
> URL: https://issues.apache.org/jira/browse/DERBY-2694
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Environment: all
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: derby-2694-v2.diff, derby-2694.diff, TestProc.java,
> TestProc_TruncateRep.java
>
>
> org.apache.derby.impl.drda.DDMWriter uses wrong algorithm to avoid splitting
> varchar in the middle of a multibyte char.
> When DMWriter finds that it has to split a varchar while sending it to client
> it checks if the last byte is a part of a multibyte char and in case it is it
> tries to find the last byte of previous char and sends only till that byte
> leaving rest of it for the next send.
> The code it uses is having a bug so it fails when the last byte its checking
> for is the third byte of a char of 3 byte length.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
