You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "A B (JIRA)" <ji...@apache.org> on 2007/06/13 19:12:26 UTC

[jira] Resolved: (DERBY-1623) Add ANSI TRIM implementation

     [ https://issues.apache.org/jira/browse/DERBY-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

A B resolved DERBY-1623.
------------------------

    Resolution: Fixed

Marking issue as RESOLVED as the patch has been committed and tinderbox results ran cleanly.  Note that the 10.3 deadline is two days away, so if you are still planning to document this issue for 10.3 (DERBY-2794), it might be good to start sooner rather than later...

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