[jira] Resolved: (DERBY-2765) Make sure that all the DTDs for character string types have correct collation assigned to them.

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor resolved DERBY-2765.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0
                   10.3.1.1

Commited a fix into main (revision 552908) and 10.3.1.1 codeline(552910) for the bug found by Dan in the Cast node. The commit comments were as follows


DERBY-2765

Dan found that Cast Node was using the collation of current schema rather than the compilation schema. This commit fixes that problem.


> Make sure that all the DTDs for character string types have correct collation assigned to them.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2765
>                 URL: https://issues.apache.org/jira/browse/DERBY-2765
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.1.1, 10.4.0.0
>
>
> All the data types in Derby have a DTD associated with them. Starting Derby 10.3, DTDs for character string types will have collation type and derivation associated with them. The numbered list in Section Collation Determination on the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478 list rules for the collation setting. But just to be sure that we have not missed anything, we should go through the Derby code and look for character string DTD creation and see if the collation is set correctly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.