Internal Website Search
51-60 of 200 resultsRefreshUpdate more than 10000 entities by an update query fails to flush changes in 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/2027 | |
Error using query with MAX() function that should fix this issue. Thank you very much for the bug report and for the useful ... ;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 with my data. awhawks Adam W. Hawks Thank you for the update | |
ObjectDB version 2.2 has been released ObjectDB 2.2 has been released and it includes important additions and fixes: Changed default configuration (enabled recovery, disabled recording). Fixed a critical database corruption bug (issue #187). Fixed | |
ClassCastException on SELECT NEW ... after UPDATE over Java RMI> DB Doctor does not fix the problem. We need guidance on how to debug and fix the problem. Thank you Emil   ... in the second database. You can fix the database with the following query | |
ObjectDB 2.6.6">issue #19). Fixed a bug in multi variable queries (issue #1801). Fixed an Explorer exception when a field in a summary view is not included in the tree/table view. Fixed a bug in caching Criteria query programs with IN | |
ObjectDB 2.3.7 Fixed a critical issue that may cause database corruption (7). Fixed automatic variable naming in criteria queries (issue #640). Fixed a bug in handling mapped super classes. Fixed | |
stress test -> com.objectdb.o.InternalException: null get it very often. Any solution/fix? A sample project is very hard, if not impossible, to create ... to reproduce and fix it. support Support Ok. I will help with a sample ... exceptions (posts #1 - #11 above) have been fixed in build 2.5.5_11. The cause | |
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 | |
combined index not used 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 filter ... so a quick fix is possible for this specific issue (although a better approach will be needed for a permanent | |
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 |