93 | Changes in detach behaviour?Changes in detach behaviour? |
93 | Changing from client server to embedded modeChanging from client server to embedded mode |
15 | Setting and Tuning of JPA Queries on which they were invoked). Flush Mode (setFlushMode) Changes made to a database using an EntityManager ... of other EntityManager instances). JPA implementations can easily make uncommitted changes visible in ... . Therefore, before a query is executed, uncommitted database changes (if any) have to be flushed to the database in |
15 | Database Explorer the Edit > Move Element commands. Saving Changes The Explorer manages an active transaction for every open ... > Save menu command commits the transaction (applying all the changes to the database). The File > Discard Changes menu command rolls back the transaction (discarding all the changes). After File > Save |
14 | Database Schema EvolutionModifications to entity classes that do not change their persistent field definitions (their schema ... after a schema change. Automatic Schema Evolution ObjectDB implements an automatic schema evolution mechanism that enables transparent use of old entity objects after schema change. When an entity object |
13 | Schema Update refactoring. Only these schema changes are specified in the configuration file. As explained in chapter 2, other schema changes are handled by ObjectDB automatically. Note: Extreme caution ... that after such changes the application is run only with the configuration that matches these changes exactly |
12 | JPA Entity Fields provider (such as Hibernate) or to change default field settings. For example: @Entity public class ... class declaration above demonstrates using field and relationship annotations to change the default ... (the Employee class in our example) is the owner. Only changes to the owner side affect the database |
1 | [ODB1] Chapter 3 - Persistent Classes must know when a persistent field is modified during a transaction because the change must be applied ... methods that perform the same accesses but also report to ObjectDB. Tracking changes in persistent ... is to apply last minute changes to persistent fields in the object just before the store. void |
1 | [ODB1] Chapter 4 - JDO Metadata is required only for changing the default. Therefore, only fields with modified behavior ... -modifier attribute makes it possible to change the default. Specifying a persistent value, as demonstrated by field f0, changes a field that is transient by default to persistent. For example, a field |
1 | [ODB1] Chapter 5 - JDO Connections values should be specified in order to change the default. In addition, the PersistenceManagerFactory ... . A transaction is always expected to be atomic, so a situation in which only some of the changes ... the changes in a related temporary file in the same directory as the database file. For instance |
