[
https://issues.apache.org/jira/browse/DERBY-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4009:
----------------------------------
Attachment: derby-4009-sample_diff.txt
Attached is a sample method change for this issue (derby-4009-sample_diff.txt).
It is not for commit. There are other methods that need to be changed, but I
wanted to post this one as a sample because I am a bit concerned about the
approach. Instead of converting directly into the buffer, I am converting to a
byte[] and then writing the bytes to the buffer. This is because I need to know
the length of the byte array up front to call ensureLength(). I am concerned
that this will have a performance impact. Does anyone have input on a more
efficient way to change these methods that write the length before the bytes.
> Accommodate length delimited DRDA strings where character length does not
> equal byte length
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-4009
> URL: https://issues.apache.org/jira/browse/DERBY-4009
> Project: Derby
> Issue Type: Sub-task
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-4009-sample_diff.txt
>
>
> Currently the drda code in server and client assumes that the byte length of
> ddm parameters is equal to the character length. In the fix for DERBY-728,
> ddm parameters such as RDBNAM will be in UTF-8 and the character and byte
> length may not match. The code needs to allow for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
