About delete

161-170 of 200Refresh
Forum
1

Maintaining referential integrity

to remove an instance of Company, it is deleted from the database, no matter if it's referenced by ... referential integrity and it is the application responsibility to avoid such deletion. The ObjectDB
Issue
1

Monitoring and Performance counters

informations about how DB is doing. It would be nice to monitor: - inserts/s, updates/s, deletes/s, reads/s - total inserts, update, deletes, reads - I/O operations/s - caches current usage - uptime from
Issue
1

NullPointer when accessing entity field

/update/delete: - we create new EntityManager, do the operation in transaction and close the EntityManager ... ), do the operations using EM in ThreadLocal, on batch end we commit transaction,delete from ThreadLocal and close
Issue
1

NullPointerException in __odbGetNumMember

Hi, When deleting an entity "Mitglied" -> everything works fine. Trying to delete another one (in a separate transaction) always causes a NullPointer Exception in __odbGetNumMember line 1 of the enhanced Mitglied class. I am unable to replicate it in a simple testcase but it always happens in
Forum
1

Objectdb Doctor

Hi, I have deleted an instance of ClassA. However, if I try to access ClassB, which has a field of type ClassA, ClassB.classA, then, rather than getting a null pointer for classB.classA, I get an enormous exception. How does the ObjectDB Doctor help?   When objects are removed/deleted from
Forum
1

odb file size doesn't shrink

Hello, why delete from ... doesnt modify size of odb? Even in in embedded mode, and in server mode i use recovery, not recording mode. When objects are deleted from the database their space is marked as unused and becomes available for future objects. The size of the database is not reduced, as
Forum
1

One transaction or two?

If I have a large number of objects to delete and then add to a PersistenceManager is it more efficient to do everything in one transaction or two? Currently my code looks like ... ().rollback(); } if(!pm.isClosed()) { pm.close(); } } Should I separate the deletes
Forum
1

orphanRemoval = true not working when CascadeType.REMOVE is disabled

try use  @OneToMany(cascade = CascadeType.REMOVE) Address entities used Employee (id=1) deleted, but Address (name_2) using other Employee (id=2) deleted too: [Address{name='name_1'}, Address{name
Forum
1

OutofMemory error with Object DB 2.0

">
Issue
1

Page #9 entry 0 (key 'bjjl') has 75 extra bytes / Unexpected last index ID: -119 (expected -116)

that these two objects will be deleted (not fixed), but still, if there is a bug that may cause storing arrays in ... got (after deleting the database file and re-running the application): MacBook:tmp bjjl$ java -cp