ObjectDB ObjectDB

Internal Website Search

1-10 of 200 resultsRefresh

unable to fix DB with Doctor (ArrayIndexOutOfBoundsException)

). DB was used by ver 2.6.9_09. I tried to fix it with ObjectDB Doctor (from ver. ver 2.6.9_09 ... How can I fix my DB? Andrzej Andrzej Domaradzki Build 2.8.6_04 includes a new version of the Doctor that can handle this specific issue. support Support

Deleting a broken reference that was fixed to null in the Explorer

Using version 2.7.4_01, we did a repair. After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support

Database Management Settings

, the recovery file can be used to fix the database. Recovery from failure is automatically applied by ObjectDB ... . When recording is enabled and recovery is disabled, recorded operations are used to automatically fix

JPA Persistable Types

must be fixed, since changing a name can cause data loss in existing databases. The @Enumerated

ObjectDB 2.4.0

to null (rather thanempty collections). Fixed a critical bug in handling a very large number of entity classes (issue #672). Fixed LockModeType.OPTIMISTIC (READ) by handling it as OPTIMISTIC_FORCE_INCREMENT. Fixed a bug in optimistic locking on find by using LockModeType.WRITE. Fixed exception

ObjectDB 2.0.0

and method finding problems. Fixed a bug in the results of IS [NOT] NULL queries. Fixed a bug in ObjectDB Doctor. Fixed persistence.xml C/S connection property to "javax.persistence.jdbc.user". Fixed a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding

again merger missing logs + objectdb exception

Zwicker Hopefully you will be able to fix the database with the Doctor before restarting the server ... . Meanwhile, have you fixed the database using the Doctor and started the system again successfully? support ... corruption. For this we probably have meanwhile a fix. As regards the query, we'll try to find

ObjectDB 2.7.0

to disable "enhancement ... is old" checks. Fixed a bug in handling remove and persist of the same object in one transaction (issue #2027). Fixed objectdb.jar to include META-INF/MANIFEST.MF as the first entry (required by Apache Karaf). Fixed a cache bug in repeating some sorts of LIKE queries

ObjectDB 2.2.9

. Changed fetch of collection elements. Fixed a bug in query plans that use an inherited index. Fixed an ArrayIndexOutOfBoundsException bug in using nested embedded objects. (issue #415). Fixed a JMX Remote - ObjectDB Enhancer Agent conflict. Fixed a ClassCastException bug in complex JOIN queries

[ODB1] Chapter 6 - Persistent Objects

is not allocated yet. Such an object ID is fixed on commit(). For example: pm.currentTransaction ... can be fixed to delete these objects before they become unreachable. JDO portable applications should not use

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