ObjectDB ObjectDB

Internal Website Search

1-10 of 116 resultsRefresh

Query only works correctly when debug printing results

on pc) the query results are only fully read back when debug printing the result contents before closing the EntityManager and Factory instance. When executing the code with the debug printing ... without the debug prints, although it exists in the database. With the debug prints, it is read

DB reading fails in debug mode in Eclipse

and IDs in the DB. My application works fine with them up to I try to launch it in debug mode in eclipse. Upon reading it in debug mode I got this exception: com.objectdb.o.UserException: Failed

Fetch Set from DB only works on debug mode

I have a class A, that contains a LinkedHashSet of another class named B. When I try to fetch that hash set, it returns a null pointer. BUT, when I run the program in debug mode, it works fine ... . In debug mode, by examining the set you load the data before closing the EntityManager. Read

Debuging query before execution

about this functionality in context of debugging and logging. Because of that, I'm for single line query with embedded values. lwalkowski Lukasz Walkowski

Query debugging configuration from class

Is there a way to show what queries are actually being executed from within a Java class? I'm getting the exception: Exception in thread "main" [ObjectDB 2.5.4_05] javax.persistence.NonUniqueResultException However, I'm unable to debug it because I don't know what the query's actually searching

stackoverflow big sur eclipse debug

stackoverflow big sur eclipse debug

Database Management Settings

for backup purposes and for debugging (by providing the ability to reproduce problems by replay ... " operations (which modify the database) have to be recorded. For debugging of query failure

JPA Entity Fields

for debugging and logging. Version values cannot be preserved for detached entity objects (explained in chapter

Database Transaction Replayer

the recorded operations. It enables reproducing problems during debugging by repeating a failure. Backup

[ODB1] Chapter 6 - Persistent Objects

, and so on). Even if you do not use the database garbage collector for production, it may be useful for debugging

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