 132 | Static Field javax.jdo.listener.InstanceLifecycleEvent int DIRTY Since: JDO 2.0 |
132 | Enum Constant javax.jdo.ObjectState DETACHED_DIRTY Since: JDO 1.0 |
132 | Enum Constant javax.jdo.ObjectState PERSISTENT_DIRTY Since: JDO 1.0 |
132 | Enum Constant javax.jdo.ObjectState PERSISTENT_NONTRANSACTIONAL_DIRTY Since: JDO 1.0 |
132 | Enum Constant javax.jdo.ObjectState TRANSIENT_DIRTY Since: JDO 1.0 |
46 | the database. ie: which objects, and which collections of objects, have been dirtied. in the jdo api ... is dirty using the static JDOHelper.isDeleted method. > You may also use JDO methods (even if your application uses JPA) so you can check if an entity object is dirty using the static JDOHelper.isDeleted |
33 | " on-persist="false" on-commit="true" />
<dirty-tracking arrays="false" />
dirty entities in ... ) is sufficient. The <dirty-tracking> element
<dirty-tracking arrays="false" />
The arrays |
26 | _INCREMENT mode affects only clean (non dirty) entity objects. Explicit lock at that mode marks the clean entity object as modified (dirty) and increases its version number by 1. The PESSIMISTIC_FORCE ... entity object as dirty and increases its version number by one (i.e. it combines PESSIMISTIC_WRITE |
26 | _INCREMENT mode affects only clean (non dirty) entity objects. Explicit lock at that mode marks the clean entity object as modified (dirty) and increases its version number by 1. The PESSIMISTIC_FORCE ... entity object as dirty and increases its version number by one (i.e. it combines PESSIMISTIC_WRITE |
15 | automatically
JDOHelper.makeDirty(employee, "projects"); // reported as dirty
em.getTransaction |