[
https://issues.apache.org/jira/browse/OPENJPA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696070#action_12696070
]
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: https://issues.apache.org/jira/browse/OPENJPA-976
> 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 http://issues.apache.org/jira/browse/OPENJPA-975. 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.
