5 | Dirty checking to generate a Json object with a list of the Users which were Added, Deleted, and Changed. That is a simple ... classes. Next a request comes in which deletes a company. So we need to send a message to the relevant |
5 | InternalException when reading a HashMap helped unfortunatelly. What helped was deleting the entity completely in explorer including all it's instances (deleting only instances did not helped) But that way we found, that another entities |
5 | OutofMemory error with Object DB 2.0" password="admin"> <dir path="/" permissions="access,modify,create,delete" /> </user> <user ... ,delete"> <quota directories="5" files="20" disk-space="5mb" /> </dir> </user> <user |
5 | Is it ok to put list or map of embeddable objects in entity ?>()) on an entity that had some Class_B instances in bList? Will they be deleted correctly from database ... previous content is automatically deleted. To see serialzable objects in the Explorer try to add |
5 | com.objectdb.o.UserException: Ambiguous entity name remove this embeddable class without deleting my database or deleting the entity it was related |
5 | unable to connect to remote server using VPN,create,delete" /> </user> <user username="$default" password="$$$###" ip="10.11.12.0-10.11.12.244"> <dir path="/$user/" permissions="access,modify,create,delete"> <quota directories="5" files="20 |
5 | Database Inconsistency or corruption) It seems that all Attributes of the updated ObjectValue are just deleted from the database. If I had detailled traces of the EntityManager or of ObjectDB, I could identified when the delete operation is executed |
1 | File lock exception on odb$ and the os allowed us to delete the files in question without any problem. In this case we weren't ... at the time but we ended up deleting the odb$ to get the app started. I'll try to recreate the problem |
1 | NullPointer when accessing entity field way: for single read/write/update/delete: - we create new EntityManager, do the operation in ... ,delete from ThreadLocal and close EM So I think there is now concurrent access on one EntityManager. In |
1 | Unexpected Exception (Error 990) with ArrayIndexOutOfBoundsException Query queryDelete = em .createQuery("DELETE FROM EventLogPersistEntry p WHERE p.id ... to the ObjectDb. I did not delete the Database file during these changes. The system where that error occured |
