Home » Search

About empty

111-120 of 200Refresh
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 ... . recovery files aren't completely empty (though are tiny, around 306 bytes). confirmed that problem
Forum
1

remove() and persist() in same transaction => Attempt to reuse an existing primary key value

) and then the special Entity (A) is empty, we remove the special Entity (A). If we add additional data for Entity ... transaction: first remove additional Data -> The special Entity (with id 1) is empty and we remove
Forum
1

Removing an entity throws exception

are empty. The query: em.createQuery("select c from Customer c").getResultList(); Code for removing ... , because when I tried to create new project as a test case for this bug, with new empty db it works
Forum
1

Removing entity class

, but there are still in ObjectDB database. The 2 tables for these entities are empty, but the tables exist, so they count ... empty database and copy the content of the old database to the new one. Ok, is there any simple way
Issue
1

Removing of an entity removes also another entity type

database and we get an empty result. This is a data lost, why this behavior can occurs? Please provide ... with type = 'interfaces' are not available anymore, the result is empty, only the ResolverMappings
Issue
1

spuriously objectdb objects have null references

that is really empty and a collection that was just not loaded. You may avoid this by using the no-detach ... as a -D command line JVM argument. If you just prefer an empty collection instead of null it wouldn't
Issue
1

Threaded Test - Failed to commit transaction: Unexpected internal exception

is currently empty                 return null;             }             catch ... differences between the JDKs) and the queue remains almost empty. Agreed - I've split the entity
Forum
1

Schema Evolution Question

was EMPTY. SUBSEQUENT restart of ObjectDB and client after attempting to access with new schema caused ... ) being read by the client using the new schema was empty.   Thank you for this report. An improved
Result
1

ObjectDB version 2.2.9

queries. Fixed a NullPointerException in querying an empty database. Fixed a online backup file
Result
1

ObjectDB version 2.4.0

recovery from failure when the recovery file is empty (issue #695). Removed EntityManager conflict