openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "B.J. Reed (JIRA)" <>
Subject [jira] Commented: (OPENJPA-976) Research the need for escape charaters for LIKE in various DB's
Date Mon, 06 Apr 2009 13:03:12 GMT


B.J. Reed commented on OPENJPA-976:

Thanks Milosz,

I went through 4 DBs when testing this (Derby, Postgres, DB2, Oracle), so I'd say you are
right that another DB could return yet another variation that isn't accounted for.  It would
have been awesome if the call would have just worked pretty much out of the box, but since
it doesn't....

Oracle is the DB that returned the "//" , but is expecting a "/" for the escape string.  I
guess it believes that since a / is an escape character, then it sends 2 to the user thinking
that the first one will be an escape char.

> Research the need for escape charaters for LIKE in various DB's
> ---------------------------------------------------------------
>                 Key: OPENJPA-976
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 2.0.0
>            Reporter: B.J. Reed
>            Assignee: B.J. Reed
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: OPENJPA-976.patch
> A new requiresSearchStringEscapeForLike field was added to the DBDictionary in
 Currently, the default is true and the OracleDictionary overwrites it to false.  Need to
investigate other DB's to see what other dictionaries would be better off as false..

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message