openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "B.J. Reed (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.
Date Tue, 17 Mar 2009 18:54:50 GMT

     [ 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-975c.patch

It appears that most DB's do want the escape character by default, Oracle is an exception,
but probably not the only one.  Latest patch cleans up the test case code and adds another
test to use a different escape string.

> 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-975c.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.


Mime
View raw message