About bulk update

131-140 of 200Refresh
Forum
0

How best to unbind all names?

My JDO application does inserts with binds, and then subsequently does bulk deletes using this code: pm.currentTransaction().begin(); Extent extent = pm.getExtent(ABC.class, true); Query q = pm.newQuery(extent); long deletedCount = q.deletePersistentAll(); pm.currentTransaction().commit
Issue
0

Mapped by fields are not initialized by JOIN FETCH in queries

), but still loading bulk of inverse fields requires performance improvement.
Issue
0

NullPointerException when using multithreading

embedded mode instead of client server mode. Persisting bulk of objects every transaction (instead
Forum
0

Server closes if large query runs out of memory

into smaller number of objects.  I understand that JPA bulk delete doesn't involve any object
Issue
0

Removing of an entity removes also another entity type

also the Issue #303. Tested with 2.7.1, 2.7.1_02 and the newest 2.7.1_03. OK. Thanks for the update. Please note that mixing direct DELETE / UPDATE database queries with EntityManager's operations is known as problematic. It is not specific to ObjectDB but general to JPA. DELETE / UPDATE JPA queries bypass
Forum
0

Entity listener - event instead of object

in updated entity. There is a problem however with accessing "old" version of object stored in ... value: {}, new value: {}, actor: {}, date: {}", new Object[] { OPERATION_TYPE_UPDATE, entityName ...                                 .toString() : null, OPERATION_TYPE_UPDATE, actorId, transTime
Forum
0

Optimization Question

to identify exactly what fields have changed from one update to the next. Currently the following sequence executes when a track update comes in: - If it’s a new track simply add it to the database. - If it's an update to an existing track, delete the entire previous entry and then add in the new
JPA Doc
0

CacheStoreMode.REFRESH

Enum Constant javax.persistence.CacheStoreMode REFRESH Insert/update entity data into cache when read from database and when committed into database. Forces refresh of cache for items read from database. Since: JPA 2.0
JPA Doc
0

CacheStoreMode.USE

Enum Constant javax.persistence.CacheStoreMode USE Insert/update entity data into cache when read from database and when committed into database: this is the default behavior. Does not force refresh of already cached items when reading from database. Since: JPA 2.0
JPA Doc
0

createNativeQuery(sqlString)

Method javax.persistence.EntityManager Query createNativeQuery(   String sqlString ) Create an instance of Query for executing a native SQL statement, e.g., for update or delete. Parameters: sqlString - a native SQL query string Returns: the new query instance Since: JPA 1.0