About Update Site

21-30 of 200Refresh
Forum
7

Update more than 10000 entities by an update query fails

Hello, following example tries to update more than 10000 entities by an update query. But only the first 10000 elements are updated. What's wrong?   public class updateMoreThan10000Elements ... .setFlushMode(FlushModeType.AUTO); { String query = "UPDATE " + MyModelElement.class
Manual
7

CRUD Database Operations with JPA [2011-02-11]

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
7

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
7

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
7

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
Forum
6

Updating Entities

with Entities not sending their updates to each other. I have two Entities in question at the moment ... . However, once a change has been made to paygradeDB after this visual load - the Employee table refuses to update ... validation checks and queries apart from UI function handlers. I also know that my code handles updating
Manual
6

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
5

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
Issue
5

JQL-Update Queries fails with activated L2-Cache

When using JQL-Update Queries it is basically not working without calling entityManager.clear ... a container the updated Entities. Scenario 1: Disabled L2 Cache, updating elements using UPDATE-Query ... database - Actual result: No changes are visble. Scenario 2: Disabled L2 Cache, updating elements using
Forum
5

ClassCastException on SELECT NEW ... after UPDATE over Java RMI

NEW ...) and UPDATE JPQL queries on the DB via the RMI interface. What we noticed is that once we UPDATE a record from the client (via the RMI interface), all SELECT NEW ... queries ... via RMI after the update. For example SELECT COUNT(*) ..., or SELECT r FROM ... all work fine.   DB