db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (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 Fri, 03 Aug 2007 18:45:52 GMT

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

Kathey Marsden updated DERBY-2668:
----------------------------------

    Attachment: derby-2668_preview_diff.txt

Before I update many masters I wanted to run a preview of the patch for this issue and the
new error format by the community.  The new error will look as below with collation always
printing with string types when comparisons are not supported.  Please let me know what you
think.

Kathey



ij> select * from sys.systables where tablename = 'T1';
ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'CHAR (TERRITORY_BASED)' are not
supported.
ij> select * from sys.systables where tablename = 1;
ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'INTEGER' are not supported.

> 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
>            Assignee: Kathey Marsden
>         Attachments: derby-2668_preview_diff.txt
>
>
> 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