[
https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681362#action_12681362
]
Milosz Tylenda commented on OPENJPA-975:
----------------------------------------
This quote from the manual
"SearchStringEscape: The default escape character used when generating SQL LIKE
clauses. The escape character is used to escape the wildcard meaning of the _
and % characters. Note: since JPQL provides the ability to define the escape
character in the query, this setting is primarily used when translating other
query languages, such as JDOQL. Defaults to "\\" (a single backslash in Java
speak)."
worries me as it suggests the resolution of this issue conflicts with JDOQL
support.
Could some more experienced developer comment on this?
Is this "always append ESCAPE to LIKE" behaviour a JDOQL requirement?
Do we care for JDO in OpenJPA 1.3 and 2.0?
> 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, OPENJPA-975doc.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.
