[
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-975.patch
Attached patch has a new field in the DBDictionary: alwaysAddSearchStringEscape
= true
The OracleDictionary sets this to false.
If this field is true, then JDBCExpressionFactory acts as it always did and
uses the searchStringEscape that is defined for the Dictionary. If it is
false, then the additional ESCAPE ('\') will not be added.
Test case also included.
> 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-975.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.
