Home » Search

About delete

161-170 of 200Refresh
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
Forum
1

Performance tuning, best practices

="/" permissions="access,modify,create,delete" />           
Forum
1

Problem with distinct select, order by and equivalent alias/attribute path

);         em.getMetamodel().entity(Location.class);         //clean up...         em.createQuery("delete from Street s").executeUpdate();         em.createQuery("delete from Location l").executeUpdate
Forum
1

Recovery file does not match db file

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

Referential Integrity

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