ObjectDB Database Search

51-60 of 60 results

Memory leak with OutOfMemoryError exception

you will have to decrease the following default ObjectDB settings: Temporary data RAM threshold . Page

Cross-platform license: Ubuntu and Windows 8

I have a machine on which I dual-boot both Ubuntu and Windows 8.  I purchased an activation code which works fine on Ubuntu but is ignored on Windows 8.  I have checked that the application is reading the right objectdb.conf by putting a temporary error in the file.  I'm assuming

Multi part paths in a composite index must have the same length

are multi value fields, unlike your simple example. Build 2.6.0_02 contains a temporary option for disabling

ObjectDB 2.7.1

Fixed a critical bug that may cause database corruption ( issue #1977 ). Improved error messages on entity operation exceptions. Fixed a NullPointerException  on cascading persist throw an unloaded collection ( issue #2049 ). Fixed the location of a temporary file for index update ( issue

performance issues, database after adding statistics, after doctor

search values. As a temporary workaround you can use a query hint to request using

ObjectDB 2.6.2

Added support of entity classes with missing implemented interfaces in the Explorer. Added method com.objectdb.Utilities.newTrackable(em, cls) for improved performance. Added a temporary workaround for NullPointerException  on query after flush ( issue #1623 ). Improved title of query result

ObjectDB 2.6.3

Added an option to disable some query execution optimizations. Added an option to exclude persistence aware enhancement ( feature request #1683 ). Added an option to use temporary files for very large transactions ( feature request #1658 ). Fixed an online backup bug (no access during backup

Calling List.removeIf makes object dirty even if nothing is removed

, so this should be fixed, and it has now been added to the issue tracking. As a temporary workaround, consider adding

ObjectDB 2.5.0

. Added a new temporary system property ("objectdb.temp.quick-file") to accelerate db opening

InternalException during EntityManager.find()

safe issue in working with temporary page files (setting "objectdb.temp.page-file", which apparently