[
https://issues.apache.org/jira/browse/OPENJPA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated OPENJPA-976:
------------------------------
Attachment: OPENJPA-976.patch
Attaching patch to get the escape string from each database in stead of having
each Dictionary class hard code it. Slight update to the test case.
If a escape string is passed into the DB Dictionary, then it uses that.
Otherwise, it attempts to get the default escape string from the JDBC layer.
All other processing is the same. There is a little bit of a kludge after
getting the escape string. Seems that what is returned from the JDBC layer
isn't quite what we were expecting because the java escape character '\' isn't
taken into account.
Thanks Jody for the idea of getting the escape character from the JDBC layer.
> 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.
