db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Khettry (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1623) Add ANSI TRIM implementation
Date Sat, 14 Apr 2007 00:12:15 GMT

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


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.

View raw message