ObjectDB ObjectDB

Internal Website Search

51-60 of 200 resultsRefresh

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

Error using query with MAX() function

an ObjectDB bug in processing large objects in queries. Please try build 2.2.2_02 that should fix this issue ... .ibm.check.cmvc2git.Test.main(Test.java:30) awhawks Adam W. Hawks Apparently the previous fix was incomplete. Please try the new build (2.2.2_03). support Support 2.2.2_03 seems to fix the problem

ObjectDB version 2.2 has been released

ObjectDB 2.2 has been released and it includes important additions and fixes: Added full support ... after index deletion. Changed default configuration (enabled recovery, disabled recording). Fixed a critical database corruption bug (issue #187). Fixed a critical bug in schema evolution of modified ancestor

ClassCastException on SELECT NEW ... after UPDATE over Java RMI

does not fix the problem. We need guidance on how to debug and fix the problem. Thank you Emil ... RecordingMetaData r For object #1 the id is Integer rather than Long in the second database. You can fix ... , and anyway, the value from the WHERE clause should not replace the existing value. We will fix the bug soon

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

stress test -> com.objectdb.o.InternalException: null

. If I decrease the load, it doesn't happen. If I increase it, I get it very often. Any solution/fix ... , we will need a sample project (even large and with no source code) in order to reproduce and fix ... exceptions (posts #1 - #11 above) have been fixed in build 2.5.5_11. The cause was unexpected order

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

combined index not used

to understand that selection and provide a fix. support Support The reason for not using the composite index was found and can be fixed. As there are too many possible combinations for covering ... the threshold from 1024 combinations to 10000 solves this issue so a quick fix is possible

ObjectDB 2.6.4

. Fixed large transaction temporary files implementation (feature request #1658). Fixed a bug in handling large objects with long primary keys as query results (issue #1717). Fixed detachment of embedded objects to collections. Fixed database page objects reuse to release to be cleared

ObjectDB can't be activated

to provide a fix as early as we can next week. support Support Yes, this is the one that failed. skolb ... , which includes an attempt to fix this issue. support Support No its not fixed, still the same error ... (Thread.java:744) skolb Sebastian Kolb I cannot see any new activation by you today. To test the 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