About fix

51-60 of 200Refresh
Result
1

ObjectDB version 2.5.5

server 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
Result
1

ObjectDB version 2.6.4

to collections. 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
Forum
1

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

Doctor does not fix the problem. We need guidance on how to debug and fix the problem. Thank you Emil ... is Integer rather than Long in the second database. You can fix the database with the following query ... should not replace the existing value. We will fix the bug soon. But meanwhile as a workaround, make
Forum
1

Error using query with MAX() function

processing large objects in queries. Please try build 2.2.2_02 that should fix this issue. Thank ... .java:30)   Apparently the previous fix was incomplete. Please try the new build (2.2.2_03). 2.2.2_03 seems to fix the problem with my data. Thank you for the update and thanks again for the bug
Issue
1

InternalException when using MEMBER OF on a large list in a query

, which is not specifically related to MEMBER OF query. A similar issue was fixed a few years ago ... , try to fix the database by running the Doctor in repair mode (even if no errors are found by ... you very much for this test - it wouldn't be possible to understand and fix the issue without this help. Build 2.6.3_04
Forum
1

Merge Issue: Attempt to reuse an existing primary key value

that the database will contain 2 B instances at the end of the test. Until that fix 3 B instances ... . The fix includes using new entity objects without merging them, which affects your test case ... launched your test case with 2.4.5 version ( so before the fix ). Test has run succesfully ... I
Issue
1

ObjectDB can't be activated

.de. Is it the one that failed? The MAC address format seems unusual so it may be related. We will try to provide a fix as early ... ? Please try build 2.5.5_06, which includes an attempt to fix this issue. No its not fixed, still the same ... .run(Thread.java:744) I cannot see any new activation by you today. To test the fix please run
Forum
1

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
Result
1

ObjectDB version 2.7.5

cascading (issue #2299). 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
Issue
1

Removed entities can be found by query in the same transaction

it again. The error didn't occur with 2.7.4_03, but with 2.7.4_04. Build 2.7.4_04 fixes issue #2280 ... after that flush were not visible to that transaction (until commit). Build 2.7.4_04 fixed it by creating ... which have another type? It is possible that the fix in build 2.7.4_04, which improves visibility