Home » Search

About update

101-110 of 200Refresh
JDO Doc
3

setReadOnly(flag)

Method javax.jdo.PersistenceManagerFactory void setReadOnly(   boolean flag ) Sets the value for whether the datastore is to be considered read-only. ReadOnly set to false specifies that no updates can be performed to the datastore, and if updates are attempted a JDOReadOnlyException is thrown. Parameters: flag - Since: JDO 2.2 See Also: getReadOnly()
JDO Doc
3

Value.updateAction

Annotation Element javax.jdo.annotations.Value ForeignKeyAction updateAction Update action to apply to any foreign key for the value. Returns: update action to apply to any foreign key for the value Default value: javax.jdo.annotations.ForeignKeyAction.UNSPECIFIED Since: JDO 2.1
Forum
3

Recursive calls with @PreUpdate annotation and Glassfish OutOfMemoryError

update(){ System.out.println(" ********* Called update() **********"); lastUpdatedDate = new ... , but the test is running embedded.  Example output of error .... ********* Called update() ********** ********* Called update() ********** ********* Called update() ********** ********* Called update
Issue
3

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
2

Pessimistic Lock Timeouts setting

the meantime, I'll use an optimistic lock and fail on stale updates. Support of pessimistic lock timeout ... is: Failed to update object com.x.y.z.ProductCodeTracking:1 - locked by another owner (error 672 ... ? My apologies, I haven't updated this thread. I have not got the issue again and I consider
Forum
2

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
2

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
2

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
2

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
2

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