 0 | side of a MEMBER OF operator (just collection navigation paths). I will check if a quick fix to support the in |
0 | with no wildcards should function as =. Build 2.4.7_17 fixes this behavior. Thanks for the quick fix |
0 | /objectdb/ Sorry. Then its probably a proxy/firewall issue here. Thank you for the quick response. meetnavpk gazal |
0 | for the quick reply. I've annotated a method with the PreRemove annotation and for testing purposes |
0 | equal. I'll consider your suggestions. Thanks for quick response! Your product is really impressive! mikhail |
0 | handling listeners and callback methods. Version 2.1.1 fixes this issue. Thanks for the quick fix. Version 2.1.1 fixed the issue. mithu1408 |
0 | Quick example:
public class MyClass {
@Column(name = "myText")
String myText;
@Temporal(TemporalType.TIMESTAMP)
@Column(name = "myDate")
Date myDate;
} Now, when querying the db with:
Query q = JPA.em().createQuery("SELECT m FROM MyClass m WHERE m.myDate LIKE |
0 | =FetchType.EAGER)
public List getRules() {
return rules;
} Thanks for the quick response... thats got it!! pedwards |
0 | LAZY. Okay, I will do just that. Thanks for the quick response. Wim So I replaced my original |
0 | ={"lastName","firstName"}) And for a single field simply @Unique on the field. Thanks for the quick reply! pezi |