About update

111-120 of 200Refresh
JDO Doc
3

ForeignKey.updateAction

Annotation Element javax.jdo.annotations.ForeignKey ForeignKeyAction updateAction The update action of this foreign key. Returns: the update action of this foreign key Default value: javax.jdo.annotations.ForeignKeyAction.RESTRICT Since: JDO 2.1
JDO Doc
3

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
JPA Doc
3

javax.persistence.EntityManager

., 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 query instance
JPA Doc
3

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
JDO Doc
3

Key.updateAction

Annotation Element javax.jdo.annotations.Key ForeignKeyAction updateAction Update action to apply to the foreign key for the key. Returns: update action to apply to the foreign key for the key Default value: javax.jdo.annotations.ForeignKeyAction.UNSPECIFIED Since: JDO 2.1
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

Eclipse plugin problem (using ObjectDB as a separate bundle)

and import into your eclise v3.62 workspace. Before attempting to run, download  and update using eclipse ... the "Close" button. 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
Forum
2

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
2

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