There is currently a note in the spec that not all databases
support the use of a trim character other than the space
character, and that use of the trim character argument
may result in queries that are not portable.
Mitesh Meswani wrote:
> Hi Linda, Mike,
>
> The TRIM functionality with ability to specify the trim character is not
> supported on Derby, Sybase, MS SQL Server and DB2. Is there any
> workaround that we can use to map EJBQL's TRIM (trim_character from
> string_primary) to sql for the dbs that do not support this functionality?
>
> Thanks,
> Mitesh
>
> -------- Original Message --------
> Subject: [IN 83672] entity-persistence INTEGRATED EJBQL: extending
> TRIM function support
> Date: Thu, 08 Dec 2005 09:25:15 -0700 (MST)
> From: Michael.Bouschen_at_Sun.COM
> Reply-To: Michael.Bouschen_at_Sun.COM
> To: Michael.Bouschen_at_Sun.COM, ejb3-toplink-ext_at_sun.com,
> ias-integrate-all_at_sun.com
>
>
>
> http://inf.central.sun.com/inf/integrationReport.jsp?id=83672
>
> Subject: EJBQL: extending TRIM function support
>
> Status Changed: Planned to Integrated.
> Integrator: Michael Bouschen
>
> Product: Sun ONE Application Server
> Codeline: java.net{trunk}
> Sub Category: entity-persistence
> Planned Date: 2005-12-08
> Integrated Date: 2005-12-08
> Impact: Low Status: Integrated Release: 9
> Affects: [ ]
>
> Related Integration Notice(s):
>
> Description: This integration extends the EJBQL compiler support for the
> TRIM function. It
> allows a TRIM function with a trim character specified and a trim
> specification
> defined as LEADING or BOTH.
>
> Reviewed by: Tom Ware
> Tests : EE QL, local tests
>
> The following file in the entity-persistence module is involved:
> M src/java/oracle/toplink/essentials/internal/parsing/TrimNode.java
>
> cvs commit output:
> Checking in
> src/java/oracle/toplink/essentials/internal/parsing/TrimNode.java;
> new revision: 1.2; previous revision: 1.1
>
> Bugs/RFE's Fixed:
>
>
>