[ 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.