ObjectDB Database Search

. The original serialized object is not affected. Cascading detach To automatically cascade a detach operation ... . ALL . When you detach an entity, the operation cascades to the entities referenced by that field, which can be a single entity or a collection of entities: @Entity class Employee { : @OneToOne ( cascade

calling the persist method or implicitly through a cascade operation. Explicit persist The following ... setting up automatic cascading persist operations. Cascading persist Marking a reference field ... operations are automatically cascaded to entities that are referenced by that field. A collection field

= Offer.class, mappedBy = "product", fetch = FetchType.LAZY, cascade = CascadeType.ALL) private Set offers ... , all "connected" offers are also removed ( cascade ). After that, when I iterate over offers in store ... and cascading delete from Product to Offer  are irrelevant to the exception. Let focus only in

bookTitle; @OneToMany( cascade = CascadeType.ALL, fetch= FetchType.EAGER) private List chapters; The Chapter ... project demonstrates a bug in cascading merge to new entity objects. A new issue was filled . 

. I supposed that makeTransient() should work somehow cascading even for the fields of the Entity ... is probably new). Cascading makeTransient may solve the issue, but may cause other problems (slower

Is there a configuration parameter to set this? dmoshal David Moshal You can set cascade delete using annotations (see also the Orphan Removal section). JDO defines similar annotations, and both JPA ... configuration. You cannot set global cascade delete since that will be too risky - you may delete the entire database. support Support

I've determined that the database is correctly initialized, looking at it from the Object Explorer, I can run the code that loads the database in a Junit test and it's initializing the children objects correctly, but in the application running in Jetty with Spring, fetching is not cascading

EntityWithFieldSettings { @Basic ( optional =false) Integer field1; @OneToOne ( cascade = CascadeType ... an exception if you try to store an entity with a null value in that field. Cascade and fetch settings

it. This operation cascades to every entity related by an association marked cascade =DETACH . If the given entity ... identity. This operation cascades to every entity related by an association marked cascade =MERGE ... , and has not been marked for removal, it is itself ignored, but the operation still cascades

using generics. Default: void/class Since: Jakarta Persistence (JPA) 1.0 CascadeType[] cascade (Optional) The operations that must be cascaded to the target of the association. When the target collection is a Map , the cascade element applies to the map value. Defaults to no operations

) 1.0 CascadeType[] cascade (Optional) The operations that must be cascaded to the target of the association. By default no operations are cascaded . Default: {} Since: Jakarta Persistence (JPA) 1.0

I enclose a Netbeans project which demonstrates the problem.  Cascading persist works, but cascading delete does not, leaving orphan objects. sjzlondon Steve Zara Thank you for this report. Apparently cascading delete has never been implemented in ObjectDB (see also "Deleting Dependent

Hello, I have a tree of entity classes that reference others using Cascade .ALL in combination with FetchType.LAZY. If I now delete a root entity using EntityManager.remove all leaf nodes will not be deleted. This only applies to the leaf nodes. If I add an additional the behaviour changes

;  @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) public long[] time;     @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private long[][] a1;     @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private long[][] a2;  

public class TransportationEvent { ... @ManyToMany(fetch = FetchType.EAGER, cascade = CascadeType ... { .... @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.PERSIST) private List transportationEvents ... ", column 'conclusions_id' by searching some forums i got syntax like @ Cascade (org.hibernate

", cascade =CascadeType.PERSIST)     private List readings = new ArrayList (); The cascade mode is required in order to persist the Reading instances with the Document   ... . support Support Ok, thank you for that. I have cascade persist set at the database configuration

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CascadeType ALL Cascade all operations Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CascadeType PERSIST Cascade the persist operation Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CascadeType MERGE Cascade the merge operation Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CascadeType REMOVE Cascade the remove operation Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CascadeType REFRESH Cascade the refresh operation Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CascadeType DETACH Cascade the detach operation Since: Jakarta Persistence (JPA) 2.0

to another entity and they both reciprocally do: EntityB:     @OneToOne( cascade = CascadeType.ALL)     EntityA entityA;   EntityA:     @OneToOne( cascade = CascadeType.ALL)     EntityB entityB;   If I make only one of the cascade , then this bug

= interfaceMy;   } } } kiki Kristijan Your code persists only the root object. If you want to cascade ... adding an annotation to a reference:   @OneToMany( cascade =CascadeType.PERSIST)   private List children; You may also specify cascading persist globally as explained in the manual. support Support

:176) at com.objectdb.o.TVS.e(TVS.java:170) at com.objectdb.o.TVS. cascade (TVS.java:157) at com ... .objectdb.o.TVS. cascade (TVS.java:157)     at com.objectdb.o.STA.C(STA.java:539)   

@GeneratedValue     private long id;     @ManyToMany(fetch = FetchType. EAGER , cascade ... = FetchType. EAGER , cascade ={CascadeType. DETACH ,CascadeType. MERGE ,CascadeType. REFRESH }, mappedBy

;   @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL, mappedBy = "parent ... , cascade = { CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH })   private ParentEntity

, cascade = CascadeType.ALL, mappedBy = "parent", orphanRemoval = true)   @MapKey(name = "childName ... long id;   @ManyToOne(fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST, CascadeType.MERGE

= "estudiante", cascade = CascadeType.ALL, orphanRemoval = true)     private List

Hello, I have a problem with the EntityManager.merge() function. I set a property value of an entity (statement) with an other entity (newSingleConstraint). newSingleValue is already persisted. I do this myself (no use of cascade because sometimes the newSingleValue is already in database

Hello, is there a way that lifecycle events like prepersist or preupdate are also fired for embeddable classes, not just for entities? My case looks as follows: @Entity public class Foo { @Id @GeneratedValue private Long id; private String description; @OneToMany( cascade = CascadeType.ALL, fetch

(TVS.java:169) 10:29:15,110 ERROR [stderr] (http--10.23.3.98-8081-5) at com.objectdb.o.TVS. cascade

( cascade = CascadeType.ALL,fetch = FetchType.EAGER) private Person person; @Index private String phn

; } @OneToMany ( cascade = CascadeType.ALL) public Map map = new HashMap (); } @Entity public static class

"ENT" that is a strong reference to that SoftReference.  Under "i", I see cascading ENT and ENT

(TimePeriod id) { this.id = id; }   @OneToMany( cascade =javax.persistence.CascadeType.ALL,fetch=javax

.java:160) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS. cascade (TVS.java:156) at com

A { @Id @GeneratedValue Long id; @OneToMany(fetch=FetchType.LAZY, cascade =CascadeType.ALL) List list

Dear all, I have entities Invoice and InvoiceItem, their relation is defined: public class Invoice implements Serializable { ... @OneToMany(mappedBy="invoice", fetch=FetchType.EAGER,              orphanRemoval=true, cascade =CascadeType

(CLT.java:156) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS. cascade (TVS.java:156) at com ... as follows; @OneToMany( cascade =CascadeType.ALL, mappedBy="z_component") @MapKey(name="z_schemeName ... .TVS.j(TVS.java:169) at com.objectdb.o.TVS. cascade (TVS.java:156) at com.objectdb.o.STA.Q(STA.java

private String secondId; @OneToOne( cascade =CascadeType.ALL) private HashMap myMap; } @Embeddable public class EmbeddableA { @OneToOne( cascade =CascadeType.ALL) private HashMap myMap; } @Embeddable public class EmbeddableB { @OneToOne( cascade =CascadeType.ALL) private HashMap myMap; } I'm am trying

, cascade =CascadeType.ALL, fetch=FetchType.EAGER) private Object payload; @OneToOne(orphanRemoval=true, cascade =CascadeType.ALL, fetch=FetchType.EAGER) private Map metadata; ... In this case the "payload

; } @Override public void setId(Long id) { this.id = id; } @OneToMany( cascade ={CascadeType.MERGE ... ; @OneToMany( cascade ={CascadeType.MERGE, CascadeType.PERSIST},        

without no reference to another entity. These entities are not persist in cascade , but explicitly by calling persist ... sure wheather this annotation is allowed when not cascade persist is used? The exception occurs

(orphanRemoval=true, cascade =CascadeType.ALL) private Map _nodes; The TaskNode contains a further Entity

{   @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL, orphanRemoval = true)  

) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS. cascade (TVS.java:156) at com.objectdb.o

Query. Then i realized that the cascade option in the entity class is ignored when doing DELETE. I

global cascade persist in an ORM file. Fixed a NullPointerException during query execution ( issue

; } @OneToMany( cascade =javax.persistence.CascadeType.ALL,fetch=javax.persistence.FetchType.EAGER