ObjectDB ObjectDB

Internal Website Search

1-10 of 200 resultsRefresh

Recovery file does not match db file

Just rebooted my production server, which had been running fine for months. When it came up, these errors started: ObjectDB 2.3.1_03] javax.persistence.PersistenceException Recovery file '/auctionologies/java/storage.odb$' does not match db file '/auctionologies/java/storage.odb' (error 145

Object comparation never matches

.NoResultException" "No matching results for a unique query (error 782)" on getSingleResult PhoneNumber

Documentation problem - license does not match implementation

Documentation problem - license does not match implementation

Strings in JPQL and Criteria Queries

Pattern Matching with Wildcards The [NOT] LIKE operator checks if a specified string matches ... characters: The percent character (%) - which matches zero or more of any character. The underscore character (_) - which matches any single character. The left operand is always the string to check

NoResultException: No matching results for a unique query

I am very often getting a "com.objectdb.o._NoResultException: No matching results for a unique query" when modifying my already persisted entities within a transaction. I cannot replicate it however because it happens infrequently. The weird thing is that the entity nevertheless gets comitted

Database Schema Evolution

the new schema for which there is a matching field in the old schema, the new field in the new entity object is initialized using the value of the matching old field in the original entity object. Fields in the new schema that do not have matching fields in the old schema are initialized

FROM clause (JPQL / Criteria API)

simply skips any outer variable value (e.g. any Country) that has no matching inner variable (e.g ... have any matching inner value it gets at least a NULL value as a matching value in the FROM

Schema Update

with persistable classes that have been renamed or moved in the IDE, with no matching schema configuration ... that after such changes the application is run only with the configuration that matches these changes exactly

JPA Lifecycle Events

of the lifecycle event. The argument can have any type that matches the actual value (e.g. in the code

Locking in JPA

if the version numbers do not match, indicating that the object has been modified by another user (using

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support