Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 38794 invoked from network); 1 Apr 2008 04:50:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Apr 2008 04:50:54 -0000 Received: (qmail 54412 invoked by uid 500); 1 Apr 2008 04:50:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 54390 invoked by uid 500); 1 Apr 2008 04:50:53 -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 54381 invoked by uid 99); 1 Apr 2008 04:50:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 21:50:53 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 04:50:15 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BA248234C0B8 for ; Mon, 31 Mar 2008 21:48:24 -0700 (PDT) Message-ID: <1040064628.1207025304761.JavaMail.jira@brutus> Date: Mon, 31 Mar 2008 21:48:24 -0700 (PDT) From: "Mamta A. Satoor (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation In-Reply-To: <23463306.1181319446433.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-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-2793: ----------------------------------- Fix Version/s: (was: 10.4.0.0) No current plans to fix it in 10.4 so I am marking fix in as unknown. I am not sure if we have been marking jira entries with no specific fix plan as unknown or next release (which in this case I guess would mean 10.5). > Ensure LIKE predicate follows correct rules for determing collation > ------------------------------------------------------------------- > > Key: DERBY-2793 > URL: https://issues.apache.org/jira/browse/DERBY-2793 > Project: Derby > Issue Type: Sub-task > Components: SQL > Reporter: Daniel John Debrunner > Assignee: Mamta A. Satoor > > The current code in LikeEscapeOperatorNode seems to only check that the collations are identical. That is not the correct mechanism for determing collation which is based upon SQL spec Section 9.13 "Collation determination" or item 12 in the DERBY-1478 wiki page. > http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478 > I think it's also essential that the (somewhat complex) logic to implement collation determination is in a single method, not repeated multiple times for each collation. > There is a TODO in LikeEscapeOperatorNode that might be related to this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.