About composite

release

2.4.7

... Improved evaluation of query plans that use composite indexes . Improved processing of queries with a large ... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ...

 
release

2.3.3

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
forum_thread

Queries are slow on a large database

Hi, I have a 12GB database with 787603 entries. It is much larger than usual and there are performances issues. I am doing small queries and they take much longer than I expect, i.e.: Get the total number of entries Get 25 consecutive entries (i.e. 0-25) Get one specific entry On average each query needs 4 to 5 minutes to return a result. I have been adviced to use indexes but they are already used through the JDO Metadata file. For instance I use this class: ... try the same query without the ORDER BY clause. A composite index in which the first component is  logTestRunId and the ... queries and the performances are much better. I will try composite index later. However there is one thing I haven't managed ...

 
issue

Sort of very large objects - out of memory

The attached test is failing with an out of memory exception when running with -Xmx512m It performs the following actions: 1) Create 5 persist threads which create and persist a large object in a loop 100 times each 2) Create 5 get threads which read 100 objects each in a loop based on object creation time and priority The message size should be around 1mb so I think there should be around 11mb of "live" data in play at any time. The objectdb cache settings are low in the config - database section is below for reference. ... objects. This requires a fix, but meanwhile, adding a composite index can solve the problem: @ Entity @ ... range query could just pick the first or last entry in the composite index (instead of scanning the entire index). Composite ...

 
release

2.3.4

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
release

2.5.1

... Improved evaluation of query plans that use composite indexes . Improved processing of queries with a large ... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ...

 
release

2.5.0

... Improved evaluation of query plans that use composite indexes . Improved processing of queries with a large ... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ...

 
release

2.3.1

... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
release

2.3.5

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
release

2.3.6

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...