107 | Cascade delete with unidirectional mappingSuppose entity A is referenced from entity B, like (A -> * B) but not actually having that reference, instead only B has @ManyToOne relationship to A and A has none. Is there a way to cascade delete ... ? vachagan Vachagan Operations are cascaded using relationships, so if you have no relationship in |
107 | 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 |
107 | Cascading deleteIs 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 |
107 | Cascading makeTransient. I supposed that makeTransient() should work somehow cascading even for the fields of the Entity ... new). Cascading makeTransient may solve the issue, but may cause other problems (slower makeTransient |
105 | Puzzler: Not getting cascades on read from Spring contextI'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 |
105 | ObjectDB 2.6.9_06 (embedded): Cascading merge resulting in duplicate objectsThis issue maybe related to issue #110 (http://www.objectdb.com/database/issue/110). Because that issue has been closed as "fixed", I am reporting this new issue. This is my class definition: @Entity public abstract class Person { @OneToMany(fetch=FetchType.EAGER, cascade=CascadeType |
105 | Error during cascaded merge = "unit", cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.EAGER) @OrderBy |
100 | Cascading (persist) with a mix of enhanced and not enhanced entitiesCascading (persist) with a mix of enhanced and not enhanced entities |
21 | Cascade.ALL with LAZY fetchtype does not clean up all references on removeHello, 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 |
14 | Updating JPA Entity Objects can be cascaded from all the entity objects that have to be stored in the database, including from ... . If global cascade persist is enabled all the reachable entity objects that are not managed |
