You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/06/23 00:47:25 UTC
[jira] Created: (DERBY-2866) Improve error message when comparing
user table and system table columns if collation doesn't match
Improve error message when comparing user table and system table columns if collation doesn't match
---------------------------------------------------------------------------------------------------
Key: DERBY-2866
URL: https://issues.apache.org/jira/browse/DERBY-2866
Project: Derby
Issue Type: Improvement
Components: SQL
Affects Versions: 10.3.1.0
Reporter: Kathey Marsden
Priority: Minor
If I create a database with TERRITORY_BASED collation and try to do a comparison between a user table column and a system table column, I get the following message. If I create it with UCS_BASIC collation there is no problem with the query. It makes sense to me that I can't compare these columns but I think it would be worthwhile to make a more informative error message since in fact normally comparisons between VARCHAR and VARCHAR are supported, just not comparisons between TERRITORY_BASED and UCS_BASIC.
Kathey
ij> connect 'jdbc:derby:enusdb;create=true;territory=en_US;collation=TERRITORY_BASED';
ij(CONNECTION1)> create table t (vc varchar(30));
0 rows inserted/updated/deleted
ij(CONNECTION1)> insert into t values('t');
1 row inserted/updated/deleted
ij(CONNECTION1)> select tableName, vc from sys.systables, t where vc = tableName;
ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported.
Bryan suggests ...
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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2866) Improve error message when comparing
user table and system table columns if collation doesn't match
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor closed DERBY-2866.
----------------------------------
> Improve error message when comparing user table and system table columns if collation doesn't match
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-2866
> URL: https://issues.apache.org/jira/browse/DERBY-2866
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.3.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> If I create a database with TERRITORY_BASED collation and try to do a comparison between a user table column and a system table column, I get the following message. If I create it with UCS_BASIC collation there is no problem with the query. It makes sense to me that I can't compare these columns but I think it would be worthwhile to make a more informative error message since in fact normally comparisons between VARCHAR and VARCHAR are supported, just not comparisons between TERRITORY_BASED and UCS_BASIC.
> Kathey
> ij> connect 'jdbc:derby:enusdb;create=true;territory=en_US;collation=TERRITORY_BASED';
> ij(CONNECTION1)> create table t (vc varchar(30));
> 0 rows inserted/updated/deleted
> ij(CONNECTION1)> insert into t values('t');
> 1 row inserted/updated/deleted
> ij(CONNECTION1)> select tableName, vc from sys.systables, t where vc = tableName;
> ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported.
> Bryan suggests ...
> 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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2866) Improve error message when comparing
user table and system table columns if collation doesn't match
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor resolved DERBY-2866.
------------------------------------
Resolution: Duplicate
This issue is duplicate of DERBY-2668.
> Improve error message when comparing user table and system table columns if collation doesn't match
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-2866
> URL: https://issues.apache.org/jira/browse/DERBY-2866
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.3.1.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> If I create a database with TERRITORY_BASED collation and try to do a comparison between a user table column and a system table column, I get the following message. If I create it with UCS_BASIC collation there is no problem with the query. It makes sense to me that I can't compare these columns but I think it would be worthwhile to make a more informative error message since in fact normally comparisons between VARCHAR and VARCHAR are supported, just not comparisons between TERRITORY_BASED and UCS_BASIC.
> Kathey
> ij> connect 'jdbc:derby:enusdb;create=true;territory=en_US;collation=TERRITORY_BASED';
> ij(CONNECTION1)> create table t (vc varchar(30));
> 0 rows inserted/updated/deleted
> ij(CONNECTION1)> insert into t values('t');
> 1 row inserted/updated/deleted
> ij(CONNECTION1)> select tableName, vc from sys.systables, t where vc = tableName;
> ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported.
> Bryan suggests ...
> 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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.