Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 75418 invoked from network); 10 Apr 2007 08:25:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Apr 2007 08:25:54 -0000 Received: (qmail 51317 invoked by uid 500); 10 Apr 2007 08:25:59 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 51273 invoked by uid 500); 10 Apr 2007 08:25:59 -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 51264 invoked by uid 99); 10 Apr 2007 08:25:59 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2007 01:25:59 -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; Tue, 10 Apr 2007 01:25:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4B9D6714079 for ; Tue, 10 Apr 2007 01:25:32 -0700 (PDT) Message-ID: <3616377.1176193532290.JavaMail.jira@brutus> Date: Tue, 10 Apr 2007 01:25:32 -0700 (PDT) From: "Andrew McIntyre (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (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:all-tabpanel ] Andrew McIntyre updated DERBY-1623: ----------------------------------- Attachment: 1623-parser-guess.diff Hi Manish, I took a stab at implementing the TRIM grammar that Bernt described. This generates a valid grammar via javacc, but only because the call to columnReference in the new characterValueExpression is commented out. Uncommented, that generates the following error: [java] Warning: Choice conflict involving two expansions at [java] line 6183, column 5 and line 6188, column 5 respectively. [java] A common prefix is: "ucase" [java] Consider using a lookahead of 2 for earlier expansion. so some work would be needed to disambiguate characterValueFunction and columnReference. And of course, execution is an entirely separate matter, but I thought this might give you some food for thought. > 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.