About delete

191-200 of 200Refresh
Forum
1

unable to connect to remote server using VPN

,create,delete" />                                 delete">                                
Issue
1

each 1-2 days objects on some objectdb level lock/block each other

,create,delete" />
Issue
1

Query fails with failed to read

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
Forum
1

Optimistic Lock Exception With No Concurrency

Hello, I have another question regarding the use of ObjectDB in my web application described in the thread https://www.objectdb.com/forum/2353: When running tests on localhost that suppose to delete ... the same test a few more times (using http delete request) eventually works, without anything changing
Forum
1

'DROP TABLE' in ODB?

Let's say I no longer need some entity in my project and after deleting all the objects of this type in database I want to remove this type from schema. How can I do this? Is there something like SQL ... this? I found a description that the DB Explorer should be capable to delete classes
Result
0

[ODB1] Chapter 6 - Persistent Objects

is automatically stored in the database when the transaction is committed (unless it is being deleted ... the object exists in the database. If an object is deleted from the database, its unique ID ... operation of bind(...), because the object is not deleted from the database, just its name
Forum
0

"Automatic" Auditing

Any ideas around how I could do "automatic" auditing of changes to objects? (An equivalent to Hibernate's Envers) Thanks. Michael. You may try the following: Define the entity class with a composite primary key [id, revision]. Never delete entity objects - alway update an object by persisting
Result
0

ObjectDB version 2.0.0

performance of database insert/update/delete operations. Changed default configuration (for improved
Result
0

ObjectDB version 2.2.0

cleanup and reusing space after index deletion. Changed default configuration (enabled recovery
Result
0

ObjectDB version 2.2.1

Version 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1. Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug. Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.