15 | 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 |
13 | 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 |
12 | 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 |
12 | 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 | 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 |
11 | 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 |
11 | 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 |
11 | 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.ALLEnum Constant javax.persistence.CascadeType ALL Cascade all operations Since: JPA 1.0 |
3 | OneToMany.orphanRemovalAnnotation Element javax.persistence.OneToMany 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 |
