[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milosz Tylenda reopened OPENJPA-975: ------------------------------------ I am afraid we have the problem with the patch applied to trunk. 1. Building the manual fails with message: 'The id "DBDictionary.SearchStringEscape" already exists in this document.' This is because of property description being doubled - it exists in generic database section and in Oracle. Should be in generic only. 2. The DBDictionary.RequiresSearchStringEscapeForLike should be rather moved from Oracle section to generic one as this is a DBDictionary property. I did not check the health of branches. > 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.