db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2765) Make sure that all the DTDs for character string types have correct collation assigned to them.
Date Tue, 03 Jul 2007 14:13:04 GMT

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

Daniel John Debrunner commented on DERBY-2765:

CAST operations currently can have the incorrect collation, thye pick up collation from the
connection's currrent schema and not the compilation schema:

CastNode line 376

		//If the result type of cast is string data type, then that data type 
		//should get it's collation type from the current schema. 
		if (externallyGeneratedCastNode && getTypeId().isStringTypeId()) {
			//set the collation type to be same as the current schema's 
			//collation type. Collation derivation is already initialized
			//to correct value by default which is "IMPLICIT"

> 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:
>            Reporter: Mamta A. Satoor
> 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.

View raw message