Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <8935225.1179515956162.JavaMail.jira@brutus>
Date: Fri, 18 May 2007 12:19:16 -0700 (PDT)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2669) If no territory attribute is not
 specified at create database time, then we should ignore the collation
 attribute if specified.
In-Reply-To: <26314879.1179473236123.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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 expected
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.

> If no territory attribute is not specified at create database time, then we should ignore the collation attribute if specified.
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2669
>                 URL: https://issues.apache.org/jira/browse/DERBY-2669
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>
> If a user specifies a create database url like following
> jdbc:derby:abcDB;create=true;collation=TERRITORY_BASED
> we should ignore the collation attribute because no territory attribute has been specified. The current Derby 10.3 code does not do that. Once this is fixed, we should add a test case for it in CollationTest.java

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