11 | Items in list are doubled, when the entity class is not enhanced, cascade= CascadeType.ALL,orphanRemoval=true) List itemList; ... getters ... - but cascaded to Item. Merging Item results in a new copy of the Item instance that becomes managed ... - but then is is persisted because of cascading from Customer. The result is 2 Item instances |
11 | Issue with orphanRemoval and multiple EntityManagers; @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, orphanRemoval=true) private List ... demonstrated 2 issues: Duplication of new objects during cascading merge - this is a known issue. You may subscribe to it, and until it is solved use workarounds (i.e. avoiding cascading merge to new |
10 | Is it ok to put list or map of embeddable objects in entity ? { (...) @OneToMany(cascade = CascadeType.ALL) List<EntityC> entityCList ... .ALL). And that's not happening... Is that a bug or are cascade operations not supported with Embeddable classes ... you can try: @Entity public class EntityA implements Serializable { (...) @OneToMany(cascade |
10 | ObjectDB JDO - foreign key constraints this behaviour? Also, how can I control cascading updates and deletes in JDO? There seems to exist ... . caused by deleting an object but keeping a reference to it). Regarding cascading operations, even if you use JDO you can still use JPA annotations to set cascading operations. Alternatively |
10 | Database Inconsistency or corruption with Cascade.ALL. That is, when merging an ObjectValue, the merge operation is propagated ... the values of the updated attribute. 3-) What I did I thought first, that ObjectDB has a problem with cascade ... markedDeleted = false; @ManyToOne private Project project; @javax.persistence.OneToMany(cascade=javax |
10 | collection of embedded objects @Entity, does the remove cascade through the whole collection? 3. Is searching through collections ... cascade operations unless it is explicitly required. Since you cannot specify cascade in @ElementCollection you will have to annotate the embedded collection with @OneToMany to cascade operations |
9 | Apparent Lazy Loading issues. state: "When the collection is a java.util.Map, the cascade element and the orphanRemoval element apply to the map value." This appears to mean that if I have cascade=CascadeType.ALL on a OneToMany map, then the cascade ONLY applies to the values, NOT to the key. This means all keys MUST be created |
2 | NullPointer when accessing persistent field.java:156) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS.cascade(TVS.java:156) at com ... ) The code being called is accessing a map declared as follows; @OneToMany(cascade=CascadeType ... .cascade(TVS.java:156) at com.objectdb.o.STA.Q(STA.java:476) at com.objectdb.o.STM.D(STM.java:390 |
2 | Tracking changes to new collections (in enhancement mode) after flush, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ModelElementImpl element; @OneToMany (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ... , cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ModelElementImpl element |
2 | Best practise loading big data; @OneToMany (cascade = CascadeType.ALL, targetEntity = MyStepBlock.class, fetch = FetchType.LAZY ... { @OneToMany (cascade = CascadeType.ALL, targetEntity = MyStep.class, fetch = FetchType ... ; @OneToMany(cascade=CascadeType.ALL) List<StepBlock> stepBlocks |
