Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <23953815.1155857594941.JavaMail.jira@brutus>
Date: Thu, 17 Aug 2006 16:33:14 -0700 (PDT)
From: "Steve Ebersole (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1623) Consider ANSI TRIM implementation
In-Reply-To: <30960721.1154454013882.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1623?page=comments#action_12428830 ] 
            
Steve Ebersole commented on DERBY-1623:
---------------------------------------

FWIW, an ANSI SQL compliant TRIM function would be fabulous.  But even a REPLACE function would allow JPA providers to emulate the ANSI SQL TRIM functionality.  Right now in Hibernate, for example, we emulate this on SQL Server and Sybase because neither support the full TRIM definition, but each do support LTRIM, RTRIM, and REPLACE which we use to achieve this emulation.

> Consider ANSI TRIM implementation
> ---------------------------------
>
>                 Key: DERBY-1623
>                 URL: http://issues.apache.org/jira/browse/DERBY-1623
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Emmanuel Bernard
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira