[
https://issues.apache.org/jira/browse/DERBY-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484510
]
Manish Khettry commented on DERBY-1623:
---------------------------------------
Yes, I agree the better thing to do is to implement the sql standard and leave
ltrim/rtrimalone.
I don't have ready access to the sql standard so I'm a litlle unsure about the
<trim character>. I'm taking it as a string literal. Looking at this page,
http://www.oreilly.com/catalog/sqlnut/chapter/ch04.html, it looks like, it is
interpreted as a string that needs to be removed. i.e.
trim(leading 'ab' from 'bac') => bac
trim(leading 'ba' from 'bac') => c
and not as I'd thought earlier a set of characters to be removed.
> 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
>
> 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.
