Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <11560807.1179519556719.JavaMail.jira@brutus>
Date: Fri, 18 May 2007 13: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_12497018 ] 

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

Laura, I selected on purpose from system table to show that system tables character columns will have collation of UCS_BASIC and the character constant 'T1' will have collation of user-schema which is TERRITORY_BASED for this db1_52 database and hence the comparison between system table character column and constant character string will fail when the comparison is done inside a user schema.

Note that character string constants pickup their collation from the current schema which in my example above is 'APP' schema which is user schema.

If the same query above is executed inside SYS schema, then the query won't fail
ij> connect 'jdbc:derby:c:/dellater/db1_52_data;create=true;collation=TERRITORY_BASED'; 
ij> set schema SYS;
0 rows selected
ij> select tablename from sys.systables where tablename='T1'; 
TABLENAME
---------------------------------------------------------------
0 rows selected

In the case above, character string constant 'T1' picked up the collation of SYS schema and hence the comparison did not fail.


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