About Index

21-30 of 200Refresh
Manual
34

Chapter 2 - JPA Entity Classes

Explains how to define and use JPA entity classes and other JPA persistable types.
Manual
25

WHERE clause (JPQL / Criteria API)

and then collected as query results. WHERE Predicate and Indexes Formally, the WHERE clause functions as a filter between the FROM and the SELECT clauses. Practically, if a proper index is available, filtering is done earlier during FROM iteration. In the above population query, if an index is defined
Result
23

ObjectDB Object Database Features [2018-01-27]

other internal caches. Indexing Single field and multi field (composite) indices. Collection and array elements are indexable (extremely fast JOIN queries). Map keys and values are indexable. Nested paths inside embedded objects are indexable. Indices are also used for fast ordering and aggregate calculations
Result
23

ObjectDB Object Database Features [2018-10-27]

other internal caches. Indexing Single field and multi field (composite) indices. Collection and array elements are indexable (extremely fast JOIN queries). Map keys and values are indexable. Nested paths inside embedded objects are indexable. Indices are also used for fast ordering and aggregate calculations
Result
23

ObjectDB Object Database Features

result cache (for repeating queries with the same arguments). Many other internal caches. Indexing Single field and multi field (composite) indices. Collection and array elements are indexable (extremely fast JOIN queries). Map keys and values are indexable. Nested paths inside embedded objects
Issue
21

combined index not used

.nodePath, a.objectsInCharge.properties.doubleValue In the class Action we have a combined index (see attachment) but in the query plan we can see that this index is not used: Query Plan Description ... ------------------------------------ [Step 1a] Scan index com.agile.hummingbird.Action[endDate] locating all the Action (a) instances
Forum
19

possible index required for improving query performance

Hi, I have the following entity class: @Entity @Table @Indices({ @Index(members={"relationshipType", "party"}), @Index(members={"relationshipType", "otherParty"}), @Index(members ... a linear way as the number of relationships and BaseObjects grow. The query is using two indexed fields
Forum
18

Composite indexes

Hi, I read your manual about defining Indexes for JPA Entities (http://www.objectdb.com/java/jpa/entity/index), but I still have some problems understanding how and when should I use them.   Let's ... ; // either true or false (...) }   Here are my questions regarding composite indexes : #1. First
Result
17

What is new in ObjectDB 2.0?

ObjectDB 2.0 supports many new features and improvements, including: Most of the features of the new JPA 2.0 and JDO 2.2 APIs. User defined IDs (primary key) and sequences. Support of unlimited index ... query execution. Support of composite indexes and using indexes in query result sort. Improved query
Forum
17

composite index not used in query

we defined a composite index for class Action: @Index(name="ssst",members={"startDate","state","subType","type"}) and an index for the OneToMany @OneToMany(fetch=FetchType.LAZY) @Index public ... ')) and (a.state = 3 and a.subType = 3 and a.type = 0 and a.startDate > ?1)) the composite index is not