[
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_p2-tests.diff
I've finally managed to iron out all the issues. Here's a quick diff of this
patch versus the previous one:
- Adds the commands switchToUtf8CcsidManager and deleteDatabase to the grammar
of TestProto.java
(The deleteDatabase is a no-op as the cleanup is done automatically using this
harness)
- Adds the UTF8 test strings that are used in TestProto.getString() to replace
the placeholders in the protocol.tests file
(The protocol.tests file does not have UTF8 strings itself)
After applying this patch, the test run posted above by Bryan passes with no
failures. I've also managed to see the database with international characters
being created and then deleted.
I'll be running derbyall overnight to make sure everything still works as
should. It should be safe to say that this does not affect suites.All.
> (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
> 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
>
>
> 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.
