Internal Website Search

Exception after update of indices of Entity class

Best practice: Database update/migration of embedded databases in products

A few entities loss after update to 2.3.7_08!

Schema-Update: Rename superclass and remove one subclass

/jpa/query/jpql/from">FROM are required in every retrieval query (update and delete queries ... /jpql/update">UPDATE queries is simpler: DELETE FROM ... [WHERE ...] UPDATE ... SET ... [WHERE ...] Besides a few exceptions, JPQL is case insensitive

for many operations, including storing, retrieving, updating and deleting database objects. and the update is propagated to the database on transaction commit.  See the update">Updating Entities section for more information about making changes to entities

copies of the same database, which are limited to READ operations. Any update to the master database ... to the master server in order to listen to updates. The updates are automatically applied

/java/jpa/CacheStoreMode/BYPASS">BYPASS - cache is not updated with new data. updated using the freshly retrieved data only when CacheStoreMode.REFRESH is used. This might be useful when the database might be updated by other applications (or using other

name is assigned to it but its content is only updated if it has changed since the last store ... updated: pm.currentTransaction().begin(); Person person = (Person)pm ... is modified) an automatic action is taken by ObjectDB to update the object lock (for example from READ

, retrieving, updating and deleting database objects, are provided in the next chapter (update, delete ... >. When using optimistic transactions, objects are not locked. Therefore, two transactions may update