8 | EM.find() is suddenly slower = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ModelElementImpl element; @OneToMany (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH |
8 | Dirty checking are automatically set to 'Detached' state. However, unless the relevant parts of the object graph have already been retrieved, they won't be retrieved for the detached object. I'm not sure how ObjectDb handles |
8 | JDO sequences from ORM file$DetachablePersistenceCapable" detachable="true" /> <class name="JdoTypes$NonDetachablePersistenceCapable" detachable="false" /> <class name="JdoTypes$CacheableClass" cacheable="true" /> <class name="JdoTypes |
8 | Updating existing persistence entries). If a detached object is modified, it has to be merged (maybe merge is your missing method?) in ... , and then you do not have detached objects and merge is not required. This is how ObjectDB Explorer |
8 | evictAll() behavior if they are implementing interfaces PersistenceCapable and Detachable after postprocesing and they do not. I spoted ... and Detachable as Isaid earlier Tomasz Tomasz Wozniak The ObjectDB 2 Enhancer doesn't use |
8 | Possible issue with Spring JPA and Embedded Paul. pedwards Paul Edwards The difference between the two tests is that Spring JPA returns detached ... after detach. Your Spring JPA test passes if you set eager fetch for that collection |
8 | Can't get arraylist/vector type attributes the EntityManager managed entity objects become detached, and content that has not been retrieved from ... ). See also "objectdb.temp.no-detach" as a possible quick workaround. support Support Loading it eagerly worked Unknown unknown |
8 | Error during cascaded merge"); List<Unit> result = query.getResultList(); Unit unit = result.get(0); em.detach ... ); } This is exactly what happens in our webapp. A unit entity gets detached, the user edits |
8 | Entity listener - event instead of object a copy of that object (maybe by JPA's detach + merge or by JDO's detachCopy). Then you may be able to compare on @PostUpdate the entity object after the update with the cloned detached entity object before the update. support Support |
8 | Failed to write the value of field using reflection (error 363) on LAZY fetch Please see this thread that also suggests a new setting ("objectdb.temp.no-detach") that may be useful for you. Regarding setting Spring Framework transactions in a way that JPA managed entities will not be detached |
