db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laura Stewart" <scotsmat...@gmail.com>
Subject Re: [jira] Commented: (DERBY-2669) If no territory attribute is not specified at create database time, then we should ignore the collation attribute if specified.
Date Fri, 18 May 2007 19:56:45 GMT
On 5/18/07, Mamta A. Satoor (JIRA) <jira@apache.org> wrote:
>    [ https://issues.apache.org/jira/browse/DERBY-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497003
> Mamta A. Satoor commented on DERBY-2669:
> ----------------------------------------
> I need to admit that I am not sure why I assumed that collation attribute with value
TERRITORY_BASED and no territory attribute should translate to UCS_BASIC for user schemas.
> It looks like then we are doing the right thing already. And following behavior is as
> ij> connect 'jdbc:derby:c:/dellater/db1_52_data;create=true;collation=TERRITORY_BASED';
> ij> select tablename from sys.systables where tablename='T1';
> ERROR 42818: Comparisons between 'VARCHAR' and 'CHAR' are not supported.
> I will go ahead and mark this as not an issue.

You seem to be selecting from a system table. Yet the documentation says

"The collation attribute applies only to user-defined tables. The
system tables use the Unicode codepoint collation."

Am I missing something?
Laura Stewart

View raw message