Home » Search

About index

191-200 of 200Refresh
Result
1

ObjectDB version 2.3.6

Version 2.3.6 Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610, #621, #625). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed
Result
1

ObjectDB version 2.5.0

when updating the schema using external classes. Fixed Doctor's index rebuilding to use NULL values
Result
1

ObjectDB version 2.5.5

ObjectDB with JBoss. Fixed query execution issues with using composite indexes. Fixed a bug in using LIKE
Result
1

ObjectDB version 2.6.1

Version 2.6.1 Added an option to disable temporary file deletion. Added support of using entity classes with missing dependent types. Added support of composite indexes with components of different lengths. Fixed a bug in reflection mode in detecting changes after flush (issue #1602). Fixed
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.7

with no persistent fields in new automatic activation of indexes. Fixed a regression bug due to changing references
Result
1

ObjectDB version 2.6.8

Version 2.6.8 Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index
Result
1

ObjectDB version 2.7.1

Version 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
Forum
1

A bidirectional OneToOne association with a shared primary key

, and you may want to set an index on the field to accelerate traversing in the other direction. Hi
Issue
1

Best practice for history tracking

for null end field? If using end field, would an index matter? what is the best way to intercept