ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh

ObjectDB version 2.1 has been released

ObjectDB 2.1 has been released and it includes important additions and fixes: Added Online Backup ... ). Fixed a bug in distinct queries (duplicates due to bad optimization). Fixed a bug in viewing TreeSet and TreeMap in the Explorer. Fixed detachment of entities by replacing proxy objects with ordinary

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

.EnumValue is not enhanced. The "fix": I discovered that if I include these in the IValue<T> interface the runtime error on attempting to persist disappears (but this does not "fix" the log enhancement ... with EnumValue::setOldValue occurs on that attempted persistence. To "fix" the error include the operations in

Failed to read DB file while online backup is running

Thank you for this report. We found something that may cause this issue, and build 2.6.2_05 should fix ... some new bug was added to the code with the previous fix. Stacktrace 1: pos = 4107765760 length ... ().createEntityManager(); } jakab Gergely Jakab Apparently an attempt to fix the issue in build

[ObjectDB 2.3.7_25] Unexpected exception (Error 990)

with these 2 Person instances without throwing an exception, but fixing these instances ... .4.0_02 fixes the Doctor as explained above. support Support I tried the new version, but the doctor ... ] null lorenz2304 Benjamin Lorenz You are right. The previous fix handled only diagnosis mode and a new

ObjectDB 2.8.6

Fixed an issue with viewing class Ids in the Explorer (see issue #2677). Fixed a regression bug (in version 2.8.5) in using AS in JOIN (issue #2666). Fixed a connection pool issue related to memory release (issue #2663). Fixed an Enhancer issue in supporting Java 9 modules and packages (issue #2657

Querying error - java.lang.ClassCastException: com.objectdb.o.STV

database or fix this database by running the Doctor in repair mode (and then verify the fix by using ... could reproduce the exception, I found the bug and fixed the problem. Version 2.2.0 that was just released includes the fix. This bug is now marked as critical since it can corrupt database files

ObjectDB 2.3.1

UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug (issue #520). Fixed a ClassCastException in using a composite index in queries (issue #521). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ($objectdb) in NetBeans RCP. Fixed

ObjectDB 2.5.7

database connection details. Fixed unstable activation in Mac OS. Fixed a bug in using FETCH JOIN in criteria queries. Fixed a bug in cascading remove when orphan removal is set. Fixed an IllegalAccessError exception when using abstract non public persistable types. Fixed the result type of a sum query on a single value.

NullPointer on query

that should be used to fix the database automatically. Did you get this error after a process kill ... been fixed yet. If this is the case and your test can cause it - posting the test could be very helpful ... transactions. At least it might be worth trying. support Support Just looked again at the page cache fix

ObjectDB 2.7.6

#2327). Fixed a regression optimistic lock exception bug (due to fix of issue #2280). Fixed a regression bug on remove and persist of an object in the same transaction (issue #2027). Fixed a bug in UPDATE queries that modify more than 10000 objects (issue #2355). Fixed a NullPointerException (issue #2302, post 43).

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