Home » Search

About fix

41-50 of 200Refresh
Result
1

ObjectDB version 2.5.1

. Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a possible deadlock on Schema Update during Multithreading activity (issue #1139). Fixed a bug in loading mapped (inverse) to-many relationship into an array field ([]) (issue #1131). Fixed a bug in loading mapped
Result
1

ObjectDB version 2.6.6

Version 2.6.6 Added support of automatic activation of new indexes (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 operator
Result
1

ObjectDB version 2.6.9

Version 2.6.9 Added support for integration with WebSphere / Liberty application server. Fixed deleting large transaction temporary files (in the experimental large transactions feature). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects
Forum
1

Out of memory

that fixes the "D:\temp\odb-synthetic" directory creation, and disables the new memory management ... is still unclear so the fix of #9 cannot be integrated. If you can provide an application (not necessarily ... . It was a false alarm of the Doctor that is now fixed in build 2.4.3_07. Please see #9 - #14
Forum
1

Remove not working

the object and removing it. No second remove in the same or any other transaction. With you fix ... across a similar problem and I thought I would share it with everyone in case it helps someone else fix ... the object that was deleted. The fix was to do a PersistenceManager.flush() before trying to gather
Forum
1

Removing an entity throws exception

It seems as an internal ObjectDB bug. Please try build 2.2.6_03 that may fix this exception ... you for fast response. The fix changed the number 51 to 34. But it looks like my db was corrupted ... file could solve the problem even with no fix, since the schema changes are gone. So either the bug
Issue
1

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 ... ) in order to reproduce and fix it. Ok. I will help with a sample then, because it's a very important ... )   The client-server exceptions (posts #1 - #11 above) have been fixed in build 2.5.5_11. The cause
Issue
1

Threaded Test - Failed to commit transaction: Unexpected internal exception

, which is now fixed in build 2.2.7_01, but the other exception is not thrown. Please check build 2.2.7_01 ... results for queries that were run by getSingleResult. The result size was evaluated to fixed size ... build 2.2.7_02 that should fix it. About the consumer / producer rate - try adding synchronized
Result
1

ObjectDB version 2.7.5_02

Version 2.7.5_02 Attempt to fix a NullPointerException (issue #2302, post 43). Version 2.7.5_01 ... listeners with JPA EntityManager. Added debug logging got persist cascading (issue #2299). Fixed a bug in restricting server access to a range of IPs (issue #2292). Fixed a bug in comparing array
Result
1

ObjectDB version 2.7.5_03

). Version 2.7.5_02 Attempt to fix a NullPointerException (issue #2302, post 43). Version 2.7.5_01 Added ... listeners with JPA EntityManager. Added debug logging got persist cascading (issue #2299). Fixed a bug in restricting server access to a range of IPs (issue #2292). Fixed a bug in comparing array fields