About Index

api-jdo

JDO Annotations

... JDO Annotations for Fields JDO Annotations for Index Definition JDO Annotations for Fetch Settings ...

 
forum_thread

Full-Text Searching

Hi, I an wondering whether there are any suggestions on design patters for doing full-text searching within ObjectDB?  Obviously, a solution would be to use Lucene for those types of searches with pointers back into ObjectDB.  Is there a way to extend ObjectDB to do that within the engine? Thanks... The ability of ObjectDB to index collections, including collections of strings, can be very useful in text ...

 
forum_thread

Query by array element

Hello, I have a class as follows: @Entity public class MyEntity {     boolean properties[]= new boolean[1024]; } I would like to query objects with feature '42': select me from MyEntity me where me.properties[42]=true Is it possible? Thank you! ... ; boolean isProperty ( int index ) { return properties [ index ] ; } } } ...

 
api-jdo

Index.columns

Columns that compose this index.(Annotation Element of javax.jdo.annotations.Index)

 
forum_thread

ObjectDB version 2.3 has been released

ObjectDB 2.3 has been released and it includes important additions and fixes: ... Fixed a bug in query plans that use an inherited index . Fixed bugs in queries on collections. ...

 
forum_thread

Extended mapping-definitions

The described feature is not available in any object-db I know, but possible with mapping to a relational DB, for example with Hibernate.   By default every entity of the real world (respectively its class) gets mapped to a java class. So cats get mapped to the java class 'Cat', dogs to 'Dog' and so on. In the project for which I'm evaluating objectDB, there 1.) will be hundreds of classes and 2.) not all classes are known at project start (an editor). ... And so apples and oranges gets mixed and no useful index can be build, etc. In Hibernate you can specify a custom mapper, ...

 
forum_thread

java.lang.NullPointerException when using ORDER BY

We are using ObjectDB 2.5.1_04. The following query causes an internal null pointer exception: SELECT r FROM RecordingMetaData AS r WHERE ((r.mapToCli != '192.168.10.200:9085' AND r.callDirection == 0)) ORDER BY r.startDateTime DESC If we remove the ORDER BY part, the query completes OK and returns the records from the DB, but obviously not in order. Here is the stack trace of the exception: ... related to your other report , i.e. using the composite index with the unexpected entry, so both issues may be solved together. ... to me try ORDER BY with a field that is not part of any index. I can reproduce the problem if a run a query where the ORDER BY filed is ...

 
issue

Negative snapshot user count exception

I found the following stack trace in my log files; it's cropped up a number of times: ... see this error message after eliminating the memory and index issues? ObjectDB Support ObjectDB - Fast ... inadequate memory, which I am sure precipitated additional index problems; I resolved the memory configuration on Sunday night.  I ...

 
release

2.2.7

... Improved cleanup and reusing space after index deletion. Changed default configuration (enabled recovery, ... Fixed a query execution bug when index with null keys is used. Fixed a bug in tracking field ...

 
release

2.2.6

... Improved cleanup and reusing space after index deletion. Changed default configuration (enabled recovery, ... Fixed a query execution bug when index with null keys is used. Fixed a bug in tracking field ...