db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2668) At the time of compilation of a comparison operation, if the collation types of the operands do not match, then we should throw a meaningful error message.
Date Tue, 26 Jun 2007 17:17:26 GMT

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

Mamta A. Satoor commented on DERBY-2668:
----------------------------------------

There is a thread on Derby list at http://www.nabble.com/comparisons-between-system-and-user-table-columns-with-TERRITORY_BASED-collation-tf3967283.html#a11261072
This talks about possible changes to the error message text. Copied portion of email from
Bryan Pendleton below


Can we make it say something like:

ERROR 42818: Comparisons between 'VARCHAR(en_US)' and 'VARCHAR(UCS_BASIC)' are not supported.

That is, sort of pack the collation information into the datatype
name somehow?



> At the time of compilation of a comparison operation, if the collation types of the operands
do not match, then we should throw a meaningful error message.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2668
>                 URL: https://issues.apache.org/jira/browse/DERBY-2668
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>
> In Derby 10.3, we are adding a new feature (DERBY-1478) which will allow character string
types to have a territory based collation (except for persistent character string type columns
from system schema). When 2 character types are compared, they should have the same collation
type associated with them. If not then Derby 10.3 will throw an exception. Currently, in Derby
10.3 codeline, the exception thrown is something like "ERROR 42818: Comparisons between 'VARCHAR'
and 'CHAR' are not supported." but this error message is misleading. The error is really for
collation mismatch. We should fix following error so it indicates the real reason behind the
exception.
> eg sql
> ij> connect 'nodb;create=true;territory=no;collation=TERRITORY_BASED'; 
> ij> select * from sys.systables where tablename = 'T1'; 
> ERROR 42818: Comparisons between 'VARCHAR' and 'CHAR' are not supported. 

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


Mime
View raw message