Internal Website Search
131-140 of 152 resultsRefreshCascading persistence through an inverse field) from the database after commit or flush. You may try synchronizing the two sides | |
Entity has be persistended,but query not fetched?; Persistence.createEntityManagerFactory("$objectdb/flush.odb"); | |
Unable to execute update query; em.flush(); | |
Query results are not up to date for entities, not primitives; personID) .executeUpdate(); em2 .flush(); em2 .clear(); tr .commit | |
Query problem after transaction commit then this could be a cache issue with a simple solution (e.g. changing flush mode from commit | |
PersistenceException: Failed to locate field> shouldn't it automatically flush it's caches if the schema evolves? or at least shouldn't | |
Where Does ObjectDB Block/Lock?. Still, transactions are concurrent, since transactions may include many operations. On commit (or flush | |
ObjectDB 2.6.2="code">NullPointerException on query after flush ( | |
Getting an error when adding activation code to conf file); em.persist(myEntity); if(i % 5000 == 0) { em.flush | |
ObjectDB 2.8.5 Fixed a bug in using AS in SELECT NEW (breaks some Spring Data JPA queries). Fixed a bug in tracking changes to new collections after flush (issue #2640). Fixed a StackOverflowError on no access permission to objectdb.conf |