[
https://issues.apache.org/jira/browse/OPENJPA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682570#comment-16682570
]
Mark Struberg commented on OPENJPA-2756:
----------------------------------------
If this escaping is not welcome - e.g. when the escaping is already performed
in the application code as a workaround for the bug - then the following can be
used to disable it back to the old behaviour:
{noformat}
<persistence-unit name="TestUnit">
<properties>
<property name="openjpa.jdbc.DBDictionary"
value="(requiresSearchStringEscapeForLike=false)" />
...
{noformat}
> PostgreSQL requires escaping of search strings in all versions
> --------------------------------------------------------------
>
> Key: OPENJPA-2756
> URL: https://issues.apache.org/jira/browse/OPENJPA-2756
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 3.0.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 3.0.1
>
>
> Our {{PostgresDictionary}} did enable the flag
> {{requiresSearchStringEscapeForLike}} only for PostgreSQL versions <= 9.0.
> But this is essentially still needed. Just tested it with PostgreSQL-11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
