[
https://issues.apache.org/jira/browse/DERBY-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago R. Espinha updated DERBY-4746:
------------------------------------
Attachment: DERBY-4746_p3.diff
This patch makes some changes on the DDMWriter to ensure that the length of the
strings is calculated based on the CCSID manager, and not just a straight call
to .length(). It also enforces that whenever a new session is started, the
CCSID manager is pushed back to EBCDIC, as all exchanges between the client and
the server must start in EBCDIC.
This is just a consolidation patch and it should not make any changes to the
outside behavior of the code. At this point, the CCSID negotiation isn't yet in
place and as such the server always stays in EBCDIC.
I have a few more changes to submit but I wanted to first check these in and
make sure everything still works as it should.
I'll be running regressions and I'll post the results shortly. Please feel free
to review the patch.
> (Server) Implement UTF8 support on DRDA
> ---------------------------------------
>
> Key: DERBY-4746
> URL: https://issues.apache.org/jira/browse/DERBY-4746
> Project: Derby
> Issue Type: Sub-task
> Affects Versions: 10.7.0.0
> Reporter: Tiago R. Espinha
> Assignee: Tiago R. Espinha
> Fix For: 10.7.0.0
>
> Attachments: DERBY-4746.diff, DERBY-4746.diff, DERBY-4746.diff,
> DERBY-4746_p2-impl.diff, DERBY-4746_p2-impl.diff, DERBY-4746_p2-tests.diff,
> DERBY-4746_p2-tests.diff, DERBY-4746_p3.diff
>
>
> I'm branching out this issue into server and client changes. Since the
> changes are incremental and small, DERBY-728 would soon become confusing if
> it had to bear the patches for both server and client.
> For future reference, some patches have actually been applied in DERBY-728.
> These **ARE** also required for the server implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
