About change

31-40 of 200Refresh
Forum
21

UPDATE query to set a new field after schema change

the changes to the DB via file->save. But when I execute a select on the DB I see that the field
Forum
21

Changes in detach behaviour?

Changes in detach behaviour?
Forum
21

Changing from client server to embedded mode

Changing from client server to embedded mode
Manual
20

Updating JPA Entity Objects

persistence, which means that changes are detected and handled automatically. Transparent Update ... yet are also persisted. Automatic Change Tracking As shown above, an update is achieved by modifying a managed ... the update. Therefore, to be able to apply database updates on commit, ObjectDB must detect changes
Manual
17

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
Manual
17

Database Explorer [2011-09-21]

collection can be modified by using the Edit > Move Element commands. Saving Changes The Explorer ... all the changes to the database). The File > Discard Changes menu command rolls back the transaction (discarding all the changes). After File > Save and File > Discard Changes, the Explorer automatically
Manual
17

Database Explorer

collection can be modified by using the Edit > Move Element commands. Saving Changes The Explorer ... all the changes to the database). The File > Discard Changes menu command rolls back the transaction (discarding all the changes). After File > Save and File > Discard Changes, the Explorer automatically
Manual
16

Database Schema Evolution

Modifications 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
Manual
15

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
Manual
13

JPA Entity Fields

provider (such as Hibernate) or to change default field settings. For example: @Entity public class ... ; } The entity class declaration above demonstrates using field and relationship annotations to change ... (the Employee class in our example) is the owner. Only changes to the owner side affect the database