[
https://issues.apache.org/jira/browse/OPENJPA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-976:
---------------------------------
Affects Version/s: (was: 2.0.0)
Fix Version/s: (was: 2.0.0)
Remaining Estimate: 0h
Original Estimate: 0h
Belatedly looking at the patch attached to this issue. It looks like Oracle is
the only DB that requires a different escape character (that we know if). In
that case I think I'd prefer to move the change to the Oracle dictionary rather
than introducing the hueristics Milosz mentioned above.
Is my understanding of the problem correct?
> Research the need for escape charaters for LIKE in various DB's
> ---------------------------------------------------------------
>
> Key: OPENJPA-976
> URL: https://issues.apache.org/jira/browse/OPENJPA-976
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Reporter: B.J. Reed
> Assignee: B.J. Reed
> Priority: Minor
> Attachments: OPENJPA-976.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> A new requiresSearchStringEscapeForLike field was added to the DBDictionary
> in http://issues.apache.org/jira/browse/OPENJPA-975. Currently, the default
> is true and the OracleDictionary overwrites it to false. Need to investigate
> other DB's to see what other dictionaries would be better off as false..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
