 20 | Hi, when going through all entity instance to find orphaned entries we get the exception ... . Create a transaction and load 10.000 entity instances 2. Check for each entity instance ... remaining was 5GB so there is also no issue. I checked my logs and found the error: Entity is not found |
20 | CriteriaBuilder to JPQL or from Entity to Primitive. What´s now? This could be the result of getting query ... operations cannot be used with queries that return values rather than entities, so these queries ... and may result in not being seen by queries: "Updating entity objects in the database using an UPDATE query |
20 | Hi, I have a usecase where I need to write the updated entity version to the database before commiting the transaction: 1. Change entity field e.g. from a to b 2. Create a change entry in database containing the new version of the entity So I need to access the version of an updated entity inside |
20 | common frames omitted We have found a workaround. We have just enhanced the entities and then it works as intended. But why this case does not perform without enhanced entities? The exception may be due to having partial enhancement. Mixing enhanced entity classes with non enhanced entity classes in |
20 | to read entities from the database. I've isolated this issue to a fairly simple test case (please see attached eclipse project). I have some test entities listed below. When I run a load test that creates, reads and updates these entities in multithreaded application it sometimes fails to read |
20 | If my entity classes have synchronized getters and setters, is it reliable for multiple threads to access a single EM's managed entities, as long as only the thread that created the EM interacts ... on the observable behavior of multithreaded code. When I run this example and examine the database, the entity |
20 | Hello, the following examples load and modify an entity, and load and remove the same entity ... ). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity ... that can still show the unexpected behaviour (i.e. remove unnecessary bundles, entity classes, JPA |
20 | Hello, it is possible to recover an entity that has been removed automatically by CascadeType.Remove. After cascade remove the removed entity will be persisted with the identical primary key. Are all broken references in other entities on this removed/persisted entity repaired again? best regards |
20 | Hello, following example tries to update more than 10000 entities by an update query ... (AccessType.FIELD)
@Entity
public static class MyModelElement {
@Id
int id ... .getTransaction().begin();
EntityA entity = new EntityA(1);
em.persist(entity |
20 | Hi, I have found a problem, when storing @Entity object in Tomcat session. When starting or ... is to create copy of @Entity class as normal POJO and use it to store in session. The problem ... on this? The exception indicates an attempt to serialize an entity object (when Tomcat stores the session before |