On 04/09/13 17:56, gsilverman wrote:
Basic JPA querying works fine:
Query query = em.createQuery("SELECT p FROM Patient p where
p.lastname=:lastname");
query.setParameter("lastname", "Silver");
List<Patient> patients = query.getResultList();
This bypasses a typed CriteriaBuilder API, so it is not 100% obvious
OpenJPA is all clear
I checked OPENJPA-2056. We have standard_conforming_strings property in
Postgresql set to OFF.
I also included this in my persistence.xml, as suggested in the article:
<property name="openjpa.jdbc.DBDictionary"
value="postgres(SearchStringEscape=\)"/>
But it had no affect.
You mentioned calling CriteriaBuilder.equal to bypass the LIKE issue, but if
CriteriaBuilder is being used internally by CXF, how could I bypass this
and use it directly in my code?
See https://issues.apache.org/jira/browse/CXF-5253
I've updated JPA and a couple of other visitors to use a strict match by
default unless a String value has a wildcard '*' or a wildcard (like)
match is always preferred
I think it makes sense to do it consistently across all the relevant
visitors, and as sucj it is not really related to this issue, but might
help anyway, try CXCF 2.7.7-SNAPSHOT a bit later or CXF 2.7.7 (due shortly)
Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/FIQL-error-unterminated-quoted-string-at-or-near-tp5733495p5733530.html
Sent from the cxf-user mailing list archive at Nabble.com.
