6 | 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 |
6 | remove & persist in same transaction => Attempt to reuse an existing primary key value. support Support ObjectDB version 2.7.0 fixes this issue. Thank you for the report. support Support Thank you for the fix. It works. btc_es BTC EmbeddedSystems Build 2.7.5_07 fixes this issue again after unknown regression. support Support A conflict was found between the fix of this issue |
6 | Merge Issue: Attempt to reuse an existing primary key value are created we expect that the database will contain 2 B instances at the end of the test. Until that fix 3 B ... 2.4.6_17. The fix includes using new entity objects without merging them, which affects your test ... am wrong, i have just launched your test case with 2.4.5 version ( so before the fix ). Test |
1 | ObjectDB 2.5.5 that is already running (avoiding further attempts). Fixed a memory issue with using ObjectDB with JBoss. Fixed query execution issues with using composite indexes. Fixed a bug in using LIKE operator in some combinations of different wildcards. Fixed a bug in handling dates (TemporalType.DATE) on some |
1 | ObjectDB 2.5.2 Framework versions (with JPA 1.0). Fixed "InternalException: InterruptedException" due to application interrupts in embedded mode. Fixed a class loading conflict with Log4j. Fixed very slow processing of a composite BETWEEN query. Fixed NullPointerException when using AND TRUE in WHERE clause (issue |
1 | InternalException when using MEMBER OF on a large list in a query an internal ObjectDB error, which is not specifically related to MEMBER OF query. A similar issue was fixed ... with the Doctor. If the error repeats, try to fix the database by running the Doctor in repair mode ... to understand and fix the issue without this help. Build 2.6.3_04 should fix it. The issue is caused |
1 | 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 |
1 | ObjectDB 2.7.5). Fixed a bug in restricting server access to a range of IPs (issue #2292). Fixed a bug in comparing array fields against parameters in queries (issue #2289). Fixed a bug in retrieving new objects of other transactions after flush (issue #2280). Fixed a bug in version 2.7.4 in automatic primary key |
1 | ObjectDB 2.0.5Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values (issue #107). Fixed a bug in handling JOIN queries with primary key fields. |
1 | ObjectDB 2.6.3 transactions (feature request #1658). Fixed an online backup bug (no access during backup operation). Fixed JOIN FETCH bugs. Fixed a performance issue with mapped by fetch. Fixed the ObjectDB Maven repository and Maven examples to work with TomEE. Fixed handling merge of an entity with PK == 0 (issue #1667). |
