23 | Updating JPA Entity ObjectsModifying existing entity objects that are stored in the database is based on transparent ... Once an entity object is retrieved from the database (no matter which way) it can simply be modified in memory ... all the modified entity objects. Therefore, entity objects that are referenced from modified entity |
23 | Server User List" ip="127.0.0.1" admin="true"> <dir path="/" permissions="access,modify,create,delete ... |modify|create|delete"> <quota directories="5" files="20" disk-space="5mb" /> </dir ... <dir path="/" permissions="access,modify,create,delete" /> <dir path="/$user/" permissions |
18 | Apache License, Version 2.0, January 2004; and You must cause any modified files to carry prominent notices stating that You changed the files ... are for informational purposes only and do not modify the License. You may add Your own attribution notices ... , provided that such additional attribution notices cannot be construed as modifying the License |
15 | Obtaining a JPA Database Connection to manipulate an ObjectDB database we need an EntityManager instance. Operations that modify database ... construction. Using an EntityTransaction Operations that modify database content, such as store ... that modify the database content, such as persist and remove. Database updates are collected and managed |
15 | Database Connection using JPA, but it is a one time operation. Once constructed, it can serve the entire application. Operations that modify ... (); // Operations that modify the database should come here. em.getTransaction().commit ... of the managed entity is not affected by the rollback and is not returned to its pre-modified state. Ending |
15 | UPDATE SET Queries in JPA/JPQL its persistence context has been modified by an UPDATE query. Therefore, it is a good practice to use a separate EntityManager for UPDATE queries. As with any operation that modifies the database, UPDATE ... method returns the number of objects that have been modified by the query. Selective Update UPDATE |
15 | Locking in JPA) is 1. In every transaction in which an entity object is modified its version number ... if the version numbers do not match, indicating that the object has been modified by another user (using ... marks the clean entity object as modified (dirty) and increases its version number by 1 |
2 | [ODB1] Chapter 3 - Persistent Classes and fields) can have any access modifiers (i.e. public, protected, package or private). 3.2 Persistent ... can never be persistent. The transient modifier can be used to exclude other fields from being stored in ... , even though they are considered transient in JDO by default. A field with a transient modifier |
2 | [ODB1] Chapter 4 - JDO Metadata is required only for changing the default. Therefore, only fields with modified behavior ... > <package name="test"> <class name="A"> <field name="f0" persistence-modifier="persistent" /> <field name="f1" persistence-modifier="none" /> <field name="f2" persistence-modifier |
1 | [ODB1] Chapter 2 - A Quick Tour that becomes persistent in line 25), and modified persistent objects (like a retrieved ArrayList, which is modified in line 29) are automatically stored in the database. Objects in memory that are reachable ... modifying class files in order to add implementation of the PersistenceCapable interface |
