[
https://issues.apache.org/jira/browse/DERBY-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B updated DERBY-1623:
-----------------------
Derby Info: (was: [Patch Available])
Fix Version/s: 10.3.0.0
Thank you for answering all of my question, Manish. I committed d1623_v3.patch
with svn # 546183:
URL: http://svn.apache.org/viewvc?view=rev&rev=546183
The _v3 patch is the same as your latest patch, but with some minor formatting
changes.
Thanks for adding this feature!
Please note: as a regular contributor to Derby we are hoping that you will take
the time to complete an ICLA, per Myrna's email here:
http://article.gmane.org/gmane.comp.apache.db.derby.devel/43960
The sooner you are able to do so, the better...
> 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
> Assignee: Manish Khettry
> Fix For: 10.3.0.0
>
> Attachments: 1623-parser-guess.diff, 1623.patch.txt,
> 1623_take2.patch.txt, AnsiTrimTest.java, compile_error.jj, d1623_v3.patch,
> sqlgrammar.jj.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.
