 0 | . I just get new build and re-run test program. It's working perfectly well now. Thanks for very quick fix. lwalkowski |
0 | must be enhanced. Thanks for the quick and helpful reply. You were exactly correct, I had neglected |
0 | . Anyway, please try build 2.4.0_03 that should fix this issue. Thank you for the quick fix. Replaced |
0 | very much, I read on: http://www.objectdb.com/java/jpa/entity/persistence-unit#Managed_Persistable_Classes And wasn't sure. I appreciate the quick reply! Phil |
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 | 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 |
