12 | JPA vs JDO - which is more efficient for OneToMany queries? field (again) or refresh it. 2) You have to persist both unless you have automatic cascade persist. In JDO all fields cascade persist operations automatically. In JPA you have to set it per field or ... one set automatic cascade globally? Seems useful for persist, delete, etc. dmoshal David Moshal |
12 | 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 |
12 | Mysterious "Attempt to persist a reference to a non managed instance" error Serializable { @Id @GeneratedValue private long id; @OneToOne(fetch=EAGER, cascade=PERSIST) public Ostrich ostrich; @ManyToMany(cascade=ALL) public Map<String, Index> entries ... that the cascading annotations would be sufficient to cause everything to be persisted (and that's worked |
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 | 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 |
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 | 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 |
9 | Remove not working) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS.cascade(TVS.java:156) at com.objectdb.o ... A { @OneToMany(mappedBy="a", cascade=CascadeType.REMOVE) private List bs ... is thrown because the removal of A is cascaded to removal of a B instance that has already been removed |
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 |
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 |
