 1 | where we had this exception we did do an object delete via Explorer (but this is not a usual case, we only cleaned ... do an object delete via Explorer (but this is not a usual case, we only cleaned up a bit) The cause |
1 | version 2.4.0. Please check if the recovery file (odb$) is empty, and if it is - just delete ... is resolved when the recovery files are deleted, does'nt seem to be any data loss. not currently able |
1 | Currently ObjectDB doesn't prevent deletion of entity objects that are in use and referenced by other entity objects, and it is the application responsibility to avoid such deletion. During development and testing it is recommended to use the ObjectDB Doctor to verify that reference integrity |
1 | path="/" permissions="access,modify,create,delete" />
|
1 | deleting all the DB files on both sides, starting a clean master and verifying it works as expected ... ,delete" />
|
1 | to explicitly define the classes, in the schema config (objectdb.config), that should be deleted. In ... different.... We think it's best to explain how the database behaves. 1) How can we delete |
1 | never shrinks when large number of objects are deleted and the only way to reclaim that space ... context to propose an answer.) ObjectDB reuses space of deleted objects but the database |
1 | records had been deleted in a successful transaction immediately prior to executing the get which errored. It is unclear what you are trying to retrieve just after deleting all the objects from |
1 | when we delete objects - there is a mechanism in our application that deals with these broken references as the costs of maintaining these specific references on deleting are very high |
1 | ">
|