13 | Eclipse plugin problem (using ObjectDB as a separate bundle) your eclise v3.62 workspace. Before attempting to run, download and update using eclipse using ... . Finally click Run (first button on last row) For the "Groovy" plugin (see update site on attached dependencies.png), once the update is done and eclipse restarted, select the _com.epimss.lab plugin, right |
13 | Unexpected exception during open the database, when indexes require updates. support Support The issue is not related to Issue #1860. It occurs ... block from objectdb.conf all works fine during opening the database. The automatic index update is not part of the objectdb.conf, this cannot be the reason. <!--<index-update enabled="true" priority="40 |
12 | Recursive calls with @PreUpdate annotation and Glassfish OutOfMemoryError, which extends a BaseEntity. The BaseEntity has a @PreUpdate as per: @PreUpdate public void update(){ System.out.println(" ********* Called update() **********"); lastUpdatedDate = new Date ... is running embedded. Example output of error .... ********* Called update |
11 | Pessimistic Lock Timeouts setting again for the prompt answers. In the meantime, I'll use an optimistic lock and fail on stale updates. Willks ... * invocationCount=50 (that is a pretty aggressive test) Exception is: Failed to update object com.x.y.z ... haven't updated this thread. I have not got the issue again and I consider |
2 | javax.persistence.FlushModeType object, the persistence provider is responsible for ensuring that all updates to the state ... of updates made to entities in the persistence context upon queries is unspecified |
2 | Removing of an entity removes also another entity type.1_03. btc_es BTC EmbeddedSystems 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 the EntityManager mechanism |
0 | 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() |
0 | Element.updateActionAnnotation Element javax.jdo.annotations.Element ForeignKeyAction updateAction Update action to apply to any foreign key for the element Returns: update action to apply to any foreign key for the element Default value: javax.jdo.annotations.ForeignKeyAction.UNSPECIFIED Since: JDO 2.1 |
0 | javax.jdo.JDOEntityManager statement, e.g., for update or delete. 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 |
0 | javax.jdo.PersistenceManagerFactory 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 |
