Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 84551 invoked from network); 3 Mar 2007 17:38:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2007 17:38:11 -0000 Received: (qmail 69292 invoked by uid 500); 3 Mar 2007 17:38:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 69254 invoked by uid 500); 3 Mar 2007 17:38:20 -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 69245 invoked by uid 99); 3 Mar 2007 17:38:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Mar 2007 09:38:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= 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; Sat, 03 Mar 2007 09:38:10 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C0220714333 for ; Sat, 3 Mar 2007 09:37:50 -0800 (PST) Message-ID: <650492.1172943470768.JavaMail.jira@brutus> Date: Sat, 3 Mar 2007 09:37:50 -0800 (PST) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2336) Enable collation based ordering for CHAR data type. In-Reply-To: <651053.1171485066130.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-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477656 ] Daniel John Debrunner commented on DERBY-2336: ---------------------------------------------- Duplicate code is a bad idea, in this case the locale is a property of the database, thus the current location (BasicDatabase) to set the code is correct. Maybe you could write up some quick design notes of how the data types will be accessing the correct locale information. I just posted in another e-mail that I think the current code that exists is taking the wrong approach, and now would be a god time to come up with a clean design. > Enable collation based ordering for CHAR data type. > --------------------------------------------------- > > Key: DERBY-2336 > URL: https://issues.apache.org/jira/browse/DERBY-2336 > Project: Derby > Issue Type: Sub-task > Components: SQL > Affects Versions: 10.3.0.0 > Reporter: Mamta A. Satoor > Attachments: DERBY_LocalFinder_CodeCleanup_diff_V01.txt, DERBY_LocalFinder_CodeCleanup_stat_V01.txt > > > I am breaking down the Parent task DERBY-1478 (Add built in language based ordering and like processing to Derby) into multiple sub tasks. One of them is to concentrate on enabling the collation based ordering on (hopefully the simplest of all the character data types) CHAR data type. This task in itself might need subtasks if it is later found that it can be subdivided into multiple smaller steps. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.