[
https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated OPENJPA-975:
------------------------------
Attachment: OPENJPA-975b.patch
Thanks Milosz for the review.
I had noticed all the "required" properties a few days ago and there was some
subtle difference on the name that I landed on.....but that logic totally
escapes me now, so I've renamed to requiresSearchStringEscapeForLike - also
want to make it as obvious as possible that it works with the
"SearchStringEscape" property.
I have it on my list of TODO's to update the documentation.
Have opened up http://issues.apache.org/jira/browse/OPENJPA-976 to do more
investigation about which DB's prefer the search string escape. At this time
my knowledge of all the DB's is rather limited, but I'll be happy to do that
research.
> Oracle needs ability to not have an escape character for search strings.
> ------------------------------------------------------------------------
>
> Key: OPENJPA-975
> URL: https://issues.apache.org/jira/browse/OPENJPA-975
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 1.2.0, 1.3.0, 2.0.0
> Environment: Oracle
> Reporter: B.J. Reed
> Assignee: B.J. Reed
> Priority: Minor
> Fix For: 1.2.0, 1.3.0, 2.0.0
>
> Attachments: OPENJPA-975b.patch
>
>
> Oracle application has a JPQL query that attempts to set a parameter to '\'.
> '\' is not a reserved character with Oracle and the query will work if you
> execute it "normally" with JDBC.
> OpenJPA automatically adds ESCAPE ('\') to every search SQL query. As a
> result the \ is interpreted as an escape indicator and the SQL will not
> execute as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
