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 | Different behavior with persist() and queried instances?: After the commit and persist calls I do close the entity manager so my object gets detached. Between ... the odb specific fields (it is an objectdb.java.util.ArrayList). However, after detaching |
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 | 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 | migration path from JPA / Hibernate writing a small JPA program that retrieves entity objects from Hibernate, detaches ... , detaches them and then persists them using ObjectDB. A tool that can > automate this process |
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 | 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 | 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 |
1 | InternalException more felixobjectdb Richard Szurgot The exception is thrown during detachment of an object (at the end of commit). Apparently the specific detached object that causes the exception has no id (primary |
1 | ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection.no-detach ! Info: Builder []: Created: com.greensoft.objectdb.test.mini.entity.Project [null](project ... /GreensoftObjectdbTestWebMini.2016-08-16.GS4223.tgz if I set experimental 'objectdb.temp.no-detach' true |
