About index

91-100 of 200Refresh
Forum
5

Unexpected exception during open the database

seems to be related to opening and closing the database for a short period, when indexes require ... {     ...     @Index     private String scopeID;     ... } if we remove the @Index annotation in ... . The automatic index update is not part of the objectdb.conf, this cannot be the reason.
JDO Doc
5

setRange(fromIncl, toExcl)

algorithm is done at the data store. Parameters: fromIncl - 0-based inclusive start index toExcl - 0-based exclusive end index, or Long.MAX_VALUE for no limit. Since: JDO 2.0
JDO Doc
5

javax.jdo.Query

- 0-based inclusive start index toExcl - 0-based exclusive end index, or Long.MAX_VALUE for no limit
JDO Doc
5

javax.jdo.annotations.Indices

javax.jdo.annotations Annotation Indices Target: Classes Annotation for a group of index constraints. Since: JDO 2.1 Index[] value The indices The indices Returns: The indices Since: JDO 2.1
Issue
5

each 1-2 days objects on some objectdb level lock/block each other

-check="true" /> <index-update ... using additional indexes, to prevent the need for repeating requests. It also makes sense to prevent ... against the data rather than against the indexes. Maybe setting query timeout could also help, at least to kill
Forum
5

ODB IndexActivation NullPointerException

Hi, We have created indexes on an existing database, which has 4.3 million objects. As soon ... ) * Batch ended at 88 I've read that: "Indexing large amount of data may take considerable processing time." Do we have to wait until index activation is finished before we can start using the database or
Forum
5

alter table

... alter table add index ... TIA There are no tables is ObjectDB. Anyway, > alter table add column ... ). > alter table add index ... Add the index definition and rebuild the database using the Object Doctor ... anything about "add index" in the links you given. TIA You can add a new index to an existing entity class
Forum
5

Mysterious "Attempt to persist a reference to a non managed instance" error

, but it's still failing. It involves two entities, Index and Ostrich. The thing to note is that the Index structure is recursive through maps; but that's never caused any problem for me in the past ... .CascadeType.*; import static javax.persistence.FetchType.*; @Entity public class Index
Forum
4

First query takes 4+ minutes to complete

) @Indices({ : // Indices building trees in client applications @Index(members={"startDate", "toExtension"}), @Index(members={"startDate", "fromExtension"}) }) public class ... an index:     @Index(members={"startDate", "startTime", "channelNumber"}) Start with a new empty
Forum
4

Performance issue in a query due to compareTo calls

(AccessType.FIELD) public class TCStep extends Identifiable { @Index private long ... , cascade = CascadeType.REMOVE) private Values valuesRef; }   @Index (members = {"step.stepNumber"}) @Entity @Access (AccessType.FIELD) public class Values extends Identifiable { @Index