Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 11438 invoked from network); 14 Apr 2007 00:12:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Apr 2007 00:12:37 -0000 Received: (qmail 4737 invoked by uid 500); 14 Apr 2007 00:12:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 4695 invoked by uid 500); 14 Apr 2007 00:12:43 -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 4685 invoked by uid 99); 14 Apr 2007 00:12:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Apr 2007 17:12:43 -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, 13 Apr 2007 17:12:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9B3E8714081 for ; Fri, 13 Apr 2007 17:12:15 -0700 (PDT) Message-ID: <3555929.1176509535633.JavaMail.jira@brutus> Date: Fri, 13 Apr 2007 17:12:15 -0700 (PDT) From: "Manish Khettry (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1623) Add ANSI TRIM implementation In-Reply-To: <30960721.1154454013882.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-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488822 ] Manish Khettry commented on DERBY-1623: --------------------------------------- Andrew Thanks for taking the time to take a look at this. I took your grammar and wrote some unit tests for it (only the parsing part). I've attached the Test. As you can see, the characterValueExpression production does not cover all the cases which can apply to trimCharacter or trimSource. Second, I was trying to make the tokens LEADING/TRAILING/BOTH as non reserved keyword. I'm not sure if that is going possible. For example in a query like: select LEADING from col. is LEADING a trimspec or is it a column name? The problem with making these reserved keywords is that it may break existing code. I will spend more time when its available to working on this-- if anyone else has thoughts on how to come up with an unambiguous grammar, please do jump in. > Add ANSI TRIM implementation > ---------------------------- > > Key: DERBY-1623 > URL: https://issues.apache.org/jira/browse/DERBY-1623 > Project: Derby > Issue Type: Improvement > Components: SQL > Reporter: Emmanuel Bernard > Assigned To: Manish Khettry > Attachments: 1623-parser-guess.diff > > > JPA is requiring databases to support this ANSI feature esp the ability to chose the trimmed character > TRIM([ [ LEADING | TRAILING | BOTH ] [ chars ] FROM ] str) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.