Home » Search

About cascade

51-60 of 200Refresh
JPA Doc
3

OneToOne.orphanRemoval

Annotation 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
Forum
3

How to Remove records from many to many relationship tables in JPA

TransportationEvent { ... @ManyToMany(fetch = FetchType.EAGER, cascade = CascadeType.PERSIST) private ... Conclusion { .... @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.PERSIST) private List ... ' by searching some forums i got syntax like @Cascade(org.hibernate.annotations.CascadeType.DELETE
Forum
2

EntityManager JPA or JDO impl and different behavior

;         }                 @OneToMany(cascade=CascadeType.PERSIST, fetch=FetchType.EAGER)         public List ... ;             displayValues.put("en", name);         }         @OneToMany(cascade=CascadeType ... /jpa/OneToMany state: "When the collection is a java.util.Map, the cascade element
Forum
2

Optimistic locking: prevent version increment on entity collection attribute

side to:     @OneToMany(mappedBy="document", cascade=CascadeType.PERSIST)     private List readings = new ArrayList(); The cascade mode is required in order to persist the Reading instances ... , should be added. Ok, thank you for that. I have cascade persist set at the database configuration
Forum
2

Eclipse plugin problem (using ObjectDB as a separate bundle)

cascaded automatically to referenced objects by default. Therefore, when you persist an object ... . Alternatively, you can turn cascading persist on - including globally (as in JDO) - see the manual ... all cascade-persist properties to true does NOT correct the problem.   I noticed that the third line
Forum
2

Issue with orphanRemoval and multiple EntityManagers

static class Organisation {         @Id         private long id;         @OneToMany(cascade ... : 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 objects). Actually in
Forum
2

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 ... because of cascading from Customer. The result is 2 Item instances - the one that you have built
Forum
2

JPA vs JDO - which is more efficient for OneToMany queries?

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 globally. I am not ... . The FAQ discusses which API should be preferred. For JPA, how does one set automatic cascade globally
Forum
2

Mysterious "Attempt to persist a reference to a non managed instance" error

implements Serializable {     @Id @GeneratedValue private long id;     @OneToOne(fetch=EAGER, cascade=PERSIST) public Ostrich ostrich;     @ManyToMany(cascade=ALL) public Map entries ... that the cascading annotations would be sufficient to cause everything to be persisted (and that's worked
Issue
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 ... dependencies )   The code being called is accessing a map declared as follows; @OneToMany(cascade ... ) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS.cascade(TVS.java:156) at com.objectdb.o