6 | Query and commit simultaneously the database at the same time using multiple threads. However, if all the threads share the same ... ) and you have to use multiple EntityManager/PersistenceManager instances, usually one per thread |
6 | Optimistic lock failed your accessing that object in the database from multiple methods simultaneously or you've got some super ... then you can try waiting before trying the transaction again or trying multiple times. jgleoj23 Joseph Gardi |
6 | Searching lists within objects: Avoid multiple Attribute instances with identical type / value by defining a composite unique ... such comparison, so it might be still more efficient to use multiple JOINs in this case. support Support Okay |
6 | em.flush(); em.clear(); loosing data and not persisting managed objects that I'm using in these entity has multiple fields that are related but takes too long to access ... with String Primary Keys, I'm going to try the other multi ID method of @IdClass and multiple @Id |
4 | High memory consumption even after close() of EntityManagerFactoryHello, we still have memory usage problems. When debugging, we have now observed a case in which the execution of multiple queries increasingly byte array were generated (about 1.5 GB) which from GC could not be released. Not even after the EntityManagerFactory closed. We created a small test |
4 | Adding new unique columns. This is indeed the only option, otherwise you will break the unique constraint with multiple objects with the same null value for the field. support Support |
4 | Is it possible to commit only specific elements? to multiple threads. Another option is to detach specific objects from the persistence context |
0 | combined index not used the next post). As you have several heavy queries with multiple JOIN operations with very slow execution |
0 | database corrupt of problems as we start now with our worldwide multiplication. Please advice what we should change in |
0 | Collision Between Different Schema Versions of Entity ClassesVersion 2.8.4 fixes a critical bug that in rare cases may cause collision between different schema versions of entity classes, when schemas have changes many times (usually more than 20 times). This bug mainly affects queries on hierarchy of multiple entity classes (i.e. a query on a super class |
