About update

61-70 of 200Refresh
Manual
19

CRUD Database Operations with JPA

it to store, retrieve, update and delete database objects. Storing New Entity Objects The following ... is a very powerful query language and chapter 4 of this manual describes it in detail. Updating and Deleting ... when the transaction is committed. Updating an existing database object is similar. You have to obtain
Manual
19

Running JPA Queries [2011-09-21]

other case. In addition, the Query interface defines a method for running DELETE and UPDATE queries: Query.executeUpdate - for running only DELETE and UPDATE queries. Ordinary Query Execution ... and UPDATE Query Execution (with executeUpdate) DELETE and UPDATE queries are executed using
Manual
19

Running JPA Queries

other case. In addition, the Query interface defines a method for running DELETE and UPDATE queries: Query.executeUpdate - for running only DELETE and UPDATE queries. Ordinary Query Execution ... and UPDATE Query Execution (with executeUpdate) DELETE and UPDATE queries are executed using
Manual
17

Database Management Settings

" synchronized="false" />   update enabled="true" priority="40" /> update> element   update enabled="true" priority="40" /> The update> element specifies how new defined
Manual
16

Storing JPA Entity Objects

too much memory. The sample code above clears the persistence context after every 10,000 persists. Updates are flushed to the database before clearing, otherwise they would be lost. Updates that are sent ... until a commit. With no explicit commit, these updates are later discarded. The combination of clear
Manual
12

Shared (L2) Entity Cache

, which are defined as constants of the CacheStoreMode enum: CacheStoreMode.BYPASS - cache is not updated with new ... that is already cached is updated using the fresh retrieved data only when CacheStoreMode.REFRESH is used. This might be useful when the database might be updated by other applications (or using
Manual
12

Database Replication and Clustering

, which are limited to READ operations. Any update to the master database is automatically propagated ... these details to connect to the master server in order to listen to updates. The updates are automatically
Manual
12

SELECT clause (JPQL / Criteria API)

objects, transparent update detection, support for delete, etc. Query results are not limited to entity ... efficiently. They are less productive with operations that update or delete entity objects, in ... and transparent update detection), but they are more lightweight, they are built faster and they consume
Manual
12

JPA Query Structure (JPQL / Criteria)

(update and delete queries have a slightly different form). The other JPQL clauses, WHERE, GROUP BY, HAVING and ORDER BY are optional. The structure of JPQL DELETE and UPDATE queries is simpler: DELETE FROM ... [WHERE ...] UPDATE ... SET ... [WHERE ...] Besides a few exceptions, JPQL is case
Manual
12

Working with JPA Entity Objects [2011-04-18]

requires using entity objects for many operations, including storing, retrieving, updating and deleting ... is detected by the owning EntityManager and the update is propagated to the database on transaction commit.  See the Updating Entities section for more information about making changes to entities