Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 62152 invoked from network); 6 Apr 2007 16:57:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Apr 2007 16:57:55 -0000 Received: (qmail 17459 invoked by uid 500); 6 Apr 2007 16:58:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 17265 invoked by uid 500); 6 Apr 2007 16:58:00 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 17253 invoked by uid 99); 6 Apr 2007 16:58:00 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2007 09:58:00 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2007 09:57:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D33B4714075 for ; Fri, 6 Apr 2007 09:57:32 -0700 (PDT) Message-ID: <27719175.1175878652862.JavaMail.jira@brutus> Date: Fri, 6 Apr 2007 09:57:32 -0700 (PDT) From: "A B (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2528) Set the correct collation type in SchemaDescriptor. The collation type will be UCS_BASIC for system schemas but it can be TERRITORY_BASED/UCS_BASIC for user schemas. In-Reply-To: <11788572.1175807912229.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487275 ] A B commented on DERBY-2528: ---------------------------- I took a quick look at DERBY2528_Collation_Type_In_Schema_v1_diff.txt and it looks good to me. Thank you in particular for the great comments--they are very helpful. > Set the correct collation type in SchemaDescriptor. The collation type will be UCS_BASIC for system schemas but it can be TERRITORY_BASED/UCS_BASIC for user schemas. > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2528 > URL: https://issues.apache.org/jira/browse/DERBY-2528 > Project: Derby > Issue Type: New Feature > Components: SQL > Affects Versions: 10.3.0.0 > Reporter: Mamta A. Satoor > Assigned To: Mamta A. Satoor > Attachments: DERBY2528_Collation_Type_In_Schema_v1_diff.txt, DERBY2528_Collation_Type_In_Schema_v1_stat.txt > > > As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, Section Collation Determination, item 2) > ) (of character string type) SQL spec Section 11.1 , General Rule 3 specifies that the character set associated with schema is used as the default character set for all . Based on this, character columns in user tables will have USER character set associated with them and hence collation type of UCS_BASIC/TERRITORY_BASED. The collation derivation will be implicit. > In order for column definition to pick up the collation from the schema, correct collation type should be available in schema. In Derby implementation world, this translates having correct collation type in SchemaDescriptor. This jira entry is to track the work required in associating collation type to a SchemaDescriptor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.