[
https://issues.apache.org/jira/browse/DERBY-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513949
]
Mamta A. Satoor commented on DERBY-2656:
----------------------------------------
Commited a fix for this in main using revision 557693. The commit comments were
as follows
This commit has 2 simple fixes (DERBY-2951 which gives assert failure and
DERBY-2656 The table will have collation type UCS_BASIC which is different than
the collation of the schema TERRITORY_BASED hence this operation is not
supported.)
The failure in DERBY-2951 is because in store, we were not using correct format
id and hence collation information was not getting written out and read from
disk. Added a test case for this in CollationTest.
The failure in DERBY-2656 was because of the bug that we were comparing
collation type for non-character types. Collation is only applicable to
character types and hence we should check for character types before comparing
the collation info. Added a test case for this one too.
> Run suites.All against a collated database
> ------------------------------------------
>
> Key: DERBY-2656
> URL: https://issues.apache.org/jira/browse/DERBY-2656
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.1.2
>
> Attachments: DERBY-2656_diff.txt, FullCollationTests_out.txt
>
>
> It would be good to leverage the existing tests to exercise the collation
> code. Investigate running all the tests against a collated database.
> Kathey
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
