[
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_sample2_diff.txt
attaching derby-4009_sample2_diff.txt that takes a different approach. This
patch will call ensureLength() based on the largest possible converted byte
length of the string. Then writes the bytes directly into the buffer and then
pokes the length in in the end.
This is similar to writeLDString in DDMWriter. I think this approach will
have less of a performance impact. The only risk is that we might potentially
expand the buffer unnecessarily, but since the buffer is big 32K and most DDM
paramters are small, I don't think this is likely to occur. I think I prefer
this approach.
> 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
> Components: Network Client, Network Server
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-4009-sample_diff.txt, derby-4009_sample2_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.
