5 | Upgrade to 2.4.1_02.cascade(TVS.java:156) at com.objectdb.o.TVS.g(TVS.java:105) at com.objectdb.o.TVS.g(TVS.java:93 |
5 | LEFT (OUTER) JOIN problem when mappedBy is defined, orphanRemoval=true, cascade= CascadeType.ALL) private List<InvoiceItem> itemList = new ArrayList |
5 | First persist takes long time objectDB.conf for the example: <cascade-persist always="auto" on-persist="true" on-commit="true |
5 | An ArrayIndexOutOfBoundsException with nested entities and enhanced entities { @ManyToOne (targetEntity = DataTypeImpl.class, cascade = {CascadeType.ALL }, fetch |
5 | Mapped By Fetch is very Slow MyEntityChild entityChild = null; @OneToOne(targetEntity = MyEntityChild.class, cascade = CascadeType |
5 | Annotate a Map field with @ElementCollection or @Basic cascading. You can also try @OneToMany(fetch=FetchType.EAGER), which may be more appropriate |
5 | OutofMemory error with Object DB 2.0 serialization="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true |
5 | Relationship Annatationshi, what is the purpose of annotating a field with a RDB relationship shuch as OneToMany. ManyToMany etc? sprintf Reuben Alfred Using these annotations is optional in ObjectDB but required by standard JPA. You still need these annotations in ObjectDB to specify cascading / fetch policy and other settings. support Support |
1 | ObjectDB 2.6.4Added memory only database mode. Added an option to cascade detachment to embedded objects. Added an option to disable reuse of database page objects. Improved release of query resources. Improved memory management in multi flush transactions. Extended detachment of embedded objects to collections |
1 | ObjectDB 2.6.0 on cascading persistence through a mapped by collection (issue #1563). Fixed a bug in using enhanced entity |
