ObjectDB ObjectDB

Internal Website Search

41-50 of 200 resultsRefresh

Removing an entity throws exception

It seems as an internal ObjectDB bug. Please try build 2.2.6_03 that may fix this exception ... it. support Support Thank you for fast response. The fix changed the number 51 to 34. But it looks like my db ... . Therefore, starting with a new database file could solve the problem even with no fix, since the schema changes

Update more than 10000 entities by an update query fails

recent builds. We will try to fix it now. support Support Please try build 2.7.5_06 that should fix this issue. support Support Hello, unfortunately the fix causes the issue https://www.objectdb.com/forum ... ; } } } btc_es BTC EmbeddedSystems Are you sure that this last fix in build 2.7.5_06

ObjectDB 2.3.7

Fixed a critical issue that may cause database corruption (issue #630). Initial attempt to enable ... of criteria queries to use aliases (issue #127). Fixed automatic variable naming in criteria queries (issue #640). Fixed a bug in handling mapped super classes. Fixed bugs in using casting in queries

ObjectDB 2.0.4

Added support for JTA and Java EE Containers (issue #8). Fixed a bug in indexing entity objects. Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced detached embedded objects. Fixed a spring transformer (LoadTimeWeaver) problem. Fixed a class loader issue

ObjectDB 2.3.6

Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610, #621, #625). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed a regression bug

ObjectDB 2.3.4

elements from required to optional. Fixed the "Negative snapshot user count" bug (issue #556). Fixed a page cache purge deadlock (issue #559). Fixed handling ;drop in client-server connection url. Fixed performance issue (fetch optimization) in range queries. Fixed cached result size evaluation

ObjectDB 2.3.2

Fixed a bug in "p.id IN :ids" queries. Fixed a bug in handling NOT = queries (issue #536). Fixed ClassCastException and NullPointerException in using a composite index in queries (issue #531). Fixed Explorer bugs: editing embedded objects and using connection urls. Fixed a NullPointerException

ObjectDB 2.8.8

field type error and internal error messages. Improved the Doctor output. Fixed a bug in using inner classes for query results. Fixed an error due to to an unused type referencing a deleted type. Fixed a primary key query issue. Fixed a bug in comparing embedded objects in queries (issue #2750

ObjectDB 2.3.0

to memory leak (issue #453). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. Fixed several NullPointerException bugs. Fixed the "Failed to generate dynamic type" exception. Fixed a bug in query plans that use an inherited

Threaded Test - Failed to commit transaction: Unexpected internal exception

to pass compilation). It reproduces the deadlock, which is now fixed in build 2.2.7_01 ... getSingleResult. The result size was evaluated to fixed size of 100 bytes, keeping much more results in cache than allowed by the defined cache size. Please try build 2.2.7_02 that should fix

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