4 | em.flush(); em.clear(); loosing data and not persisting managed objects build 2.2.3_06 that should fix this bug. support Support This fix works except when the primary key ... should fix it. As a side note - ObjectDB doesn't limit the length of primary keys, but large strings |
4 | Possible Bug in MEMBER OF the WHERE clause. Build 2.3.3_01 provides a temporary fix that makes your query work. Still SIZE and IS EMPTY are not supported yet and this should be fixed in future versions. support Support Thanks for the fix. Now it works. I hope you add comprehensive support for inverse collection fields in |
4 | Homepage and forum nearly inaccessible Hornbach Just verified that the problem is fixed here in Canada too - one or two second response time. Thank you ObjectDB for your quick fix, which is what we all now expect from you, as normal ... and for other unrelated jars). As a fix we moved the Maven server today to another node in a different location |
4 | TYPE Expression.3.4_02 includes a partial fix and the following test should work: package com.objectdb.test.bug ... and post the revised test. support Support Build 2.3.4_03 should fix also the type literals problem ... Alexander Adam Build 2.3.4_04 should complete the fix of this problem. support Support |
0 | Server Deadlock Thank you for this report. Build 2.2.9_01 should fix the deadlock. support Support Build 2.3.7_04 fixes another case of this deadlock that was not covered by the previous fix. support Support |
0 | ObjectDB 2.0.1Fixed a bug in lazy loading of instances of non enhanced classes. Fixed a bug in using the Replayer with no updates to the database. Fixed an activation bug. |
0 | Page cache File handling produced an java.io.IOException: Negative seek offset transactions. Version 2.6.7 should fix this bug. support Support Version 2.6.7 don't fix the bug ... Also Version 2.6.7_1 don't fix the bug: Exception in thread "Thread-174" [ObjectDB 2.6.7_01] Unexpected |
0 | Unexpected error when loading all entity instance again after already fixing the database with the ObjectDB Doctor? support Support Hello, yes. I repaired the database ... is ready at: db/smartcal.odb.fixed I enabled Recording so next time I will be able to attach a record ... doppelrittberger Markus Ritter Build 2.7.1 should fix this bug. This is probably the most critical bug in ObjectDB |
0 | version 2.4.5+ with GlassFish 3.1.2, errors when runs application. Version 2.4.4 worked but not 2.4.5 or later.getResultList(JpaQuery.java:686) lucobjdb Luc Have you tried 2.4.5 or 2.4.5_03? Because 2.4.5_03 fixes ... that the problem was fixed in 2.4.5_03. If you see this error when using a newer ObjectDB build - please reopen it. support Support Build 2.4.6 fixes another regression issue with GlassFish, which may be related to this report. support Support |
0 | query.getResultList() throws ClassCastException and for the test. Version 2.3.1 fixes the exception. Some performance tips for this test: You can improve ... . Once I fixed my test, the ID lookups are 5x+ faster on existent entities. Ok, good to know. I've ... a more complete fix for this problem (following issue #531). support Support |
