 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 |
0 | in this project... Again, thanks for the quick support here! An update on this topic: 1 |
0 | /query/jpql/delete#Selective_Deletion_) ? Thanks for your quick support, Have a nice weekend, Jeroen. JeroenH |
0 | that demonstrates the issue. Please try version 2.5.6 that should fix it. Perfect - it is fixed - Thanks a lot - was very quick - I am impressed. EKK |
0 | to the department 1 entity." Wow, your answer was quick, thanks! In the meantime I checked spec |
0 | it. But we will check if we can release a quick patch to support this without the workaround. ObjectDB version |
0 | .objectdb.Server.main(Server.java:66) I just ran a quick test and couldn't reproduce the problem:
package |