16 | Merge Issue: Attempt to reuse an existing primary key value object share the same child on a ManyToMany relationship with Cascade.ALL constraint. public final ... private String name; @ManyToMany(cascade = { CascadeType ... (); } @Entity static class A { @OneToMany(cascade=CascadeType |
14 | How to Remove records from many to many relationship tables in JPA TransportationEvent { ... @ManyToMany(fetch = FetchType.EAGER, cascade = CascadeType.PERSIST) private List ... { .... @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.PERSIST) private List ... searching some forums i got syntax like @Cascade(org.hibernate.annotations.CascadeType.DELETE_ORPHAN |
13 | Optimistic locking: prevent version increment on entity collection attribute", cascade=CascadeType.PERSIST) private List<Reading> readings = new ArrayList<Reading>(); The cascade mode is required in order to persist the Reading instances with the Document instance ... Support Ok, thank you for that. I have cascade persist set at the database configuration level |
13 | EntityManager JPA or JDO impl and different behavior; } @OneToMany(cascade=CascadeType.PERSIST, fetch=FetchType.EAGER) public List ... ; displayValues.put("en", name); } @OneToMany(cascade=CascadeType ... ://www.objectdb.com/api/java/jpa/OneToMany state: "When the collection is a java.util.Map, the cascade |
13 | Eclipse plugin problem (using ObjectDB as a separate bundle) (unlike JDO) persist is not cascaded automatically to referenced objects by default ... - otherwise you get this exception. Alternatively, you can turn cascading persist on - including globally (as ... have NOT written one line of JPA code!! Setting all cascade-persist properties to true does NOT correct |
12 | 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 |
12 | OptimisticLockException it is modified. Presumably that a blocking operation? Next question: how do I automatically cascade the refresh (ie for collections held by the object modified)? Can cascading refresh be set in the conf ... exceptions. Cascading refresh is set by annotations. support Support sorry for all the questions |
3 | CascadeType.DETACHEnum Constant javax.persistence.CascadeType DETACH Cascade detach operation Since: JPA 2.0 |
3 | OneToOne.orphanRemovalAnnotation Element javax.persistence.OneToOne boolean orphanRemoval (Optional) Whether to apply the remove operation to entities that have been removed from the relationship and to cascade the remove operation to those entities. Default value: false Since: JPA 2.0 |
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 |
