118 | Cascading persistence through an inverse fieldHi! I was playing with cascading persistence with @ManyToMany and inverse @ManyToMany fields, and I noticed that I can only get cascading persistence in one direction. If the "owner ... -related code to keep it simple. @Entity public class PointCollection { @ManyToMany(cascade |
116 | Cascading merge() leading to "Attempt to persist a reference to a non managed instance" error with a parent/child relationship and cascading merge() operations. The parent has an application defined id ... (cascade = CascadeType.ALL) @SuppressWarnings("unused") private Parent owner; public ... . Cascading merge to new entity objects (the Parent instances in your code) is currently broken |
114 | OneToMany and cascade delete problem { @OneToMany(targetEntity = Offer.class, mappedBy = "product", fetch = FetchType.LAZY, cascade = CascadeType ... . The problem is, that after removing product, all "connected" offers are also removed (cascade ... .test.bug.forum.T501.main(T501.java:73) I think that the Offer class and cascading delete from Product |
114 | Memory leak while merging parent with No Cascade annotation with children comparing Cascade.ALL (or Cascade.MERGE ) to nothing. Tested with last version of Object Db ( 2.5.5 ... MyEntity { @Id private String name; @ManyToMany(cascade |
114 | Cascade type annotaion on an embeddable type cascading is not required for the embedded objects themselves. There could be some specific case in which specifying Embedded is needed and it is related to cascading. If the embedded object contains a reference to an entity object with cascading annotation, it will be ignored by ObjectDB |
113 | Double persist of Entity field with Cascade.ALL bookTitle; @OneToMany(cascade= CascadeType.ALL, fetch= FetchType.EAGER) private List<Chapter ... Your test project demonstrates a bug in cascading merge to new entity objects. A new issue was filled |
23 | I can't get cascading delete to work in JDOI enclose a Netbeans project which demonstrates the problem. Cascading persist works, but cascading ... cascading delete has never been implemented in ObjectDB (see also "Deleting Dependent Objects" on this old documentation page). Build 2.7.5_04 implements cascading delete in JDO. Your NetBeans |
23 | New entity objects are duplicated on merge cascadingWhen merge is cascaded to a new entity object that has not been persisted ... = GenerationType.AUTO) private Long id; @OneToMany(cascade= CascadeType ... another new / dirty entity object by a reference with cascading persist disabled. The following test |
23 | Sometimes cascade persist does not work during commit and the commit persists the entities B automatically by cascading. But sometimes the cascading doesn't ... ? // persist configuration: <cascade-persist always="auto" on-persist="true" on-commit="true" /> public ... int id; @Basic String strValue; @OneToMany (cascade |
22 | Issue with cascade delete & add/remove of Address which cascades deletes (orphanRemoval=true) to its children which is what we want ... Entities within the collection of a Contact when we delete the Contact? Is that cascaded or do we need ... public static class Contact { private String name = null; @OneToMany(cascade |
