102 | orphanRemoval = true not working when CascadeType.REMOVE is disabled) private Set<Address> addresses; I'm expecting, that removing Employee from db, addresses ... try use @OneToMany(cascade = CascadeType.REMOVE) Address entities used Employee (id=1) deleted |
101 | Question: remove and recreate an object, do the references survive ? that would remove the orphane references) ? hgzwicker Hans-Georg Zwicker References should survive |
20 | Removed entities can be found by query in the same transactionHello, we opened a transaction, load an entity from database and removed this entity by em.remove(). Afterwards the entity can be load again by query although the resulted entity have an attribute __odbtracker/m (type STA, value=Persistent-Deleted-Flushed) which shows that the entity is deleted |
20 | Allow removal of entity class from ObjectDB & Explorer to its data structure. When an entity class becomes unnecessary, we should be able to remove |
20 | Persist & remove in same transaction Remove the entity object, EntityManager is flushed & cleared, Transaction is not committed Count |
18 | Working with JPA Entity Objects: New, Managed, Removed and Detached. When an entity object is initially created its state is New. In ... the EntityManager’s remove method within an active transaction. The entity object changes its state from Managed to Removed, and is physically deleted from the database during commit. More details on object |
16 | CRUD Database Operations with JPA a managed object (usually by retrieval) and invoke the remove method within the context of an active transaction: em.getTransaction().begin(); em.remove(p); // delete entity em ... . The entity object is marked for deletion by the remove method and is physically deleted from the database |
16 | Shared (L2) Entity Cache objects can be removed from the cache by one of the evict methods: // Remove a specific entity object from the shared cache: cache.evict(MyEntity.class, Long.valueOf(id)); // Remove ... cache by removing all the cached entity objects: cache.evictAll(); The Cache interface and its methods are unnecessary in most applications. |
1 | [ODB1] Chapter 6 - Persistent Objects section 3.2. The Utilities.unbind(...) method removes an object name: import com.objectdb.Utilities ... .currentTransaction().commit(); Removing a name also requires an active transaction. When the transaction is committed, the name is removed from the database. Notice that unbind(...) is not exactly an inverse |
1 | javax.jdo.JDOEntityManager store. This method must be called in an active transaction. The data store object will be removed ... pc) void detach(Object entity) Remove the given entity from the persistence context, causing a managed entity to become detached. Remove the given entity from the persistence context, causing |
