openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.
Date Thu, 02 Apr 2009 19:31:12 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dick reassigned OPENJPA-975:
------------------------------------

    Assignee: B.J. Reed  (was: Michael Dick)

> 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.0.4, 1.2.2, 1.3.0, 2.0.0
>
>         Attachments: OPENJPA-975-trunk.patch, OPENJPA-975c.patch, OPENJPA-975c_1.0.x.patch,
OPENJPA-975c_1.0.x.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