ObjectDB ObjectDB

Internal Website Search

21-30 of 200 resultsRefresh
106

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
101

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 ... or false (...) } Here are my questions regarding composite indexes : #1. First
98

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
97

Composite Index error 328

( { @javax.jdo.annotations.Index(members = {"id","pwd","access"}) } ) public class ... _01] javax.persistence.PersistenceException Invalid index path 'id' in type persistence.jpa.models ... .UserException: Invalid index path 'id' in type persistence.jpa.models.UsrlistEntity at com.objectdb.o.MSG
37

Database Management Settings

" synchronized="false" />   <index-update enabled="true" priority="40" /> <query-cache results ... , to avoid thread competition that leads to poor performance. The <index-update> element   <index-update enabled="true" priority="40" /> The <index-update> element specifies how newly defined indexes
25

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
23

WHERE clause (JPQL / Criteria API)

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 on the population field ObjectDB can use that index
21

ObjectDB Object Database Features

). 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 are indexable. Indices are also used for fast ordering and aggregate
20

Problem using "and" for joined entities and indexed fields

Using @Index for fields and filter more than one field with "and" predicate ends in empty result list. public class IndexTest {     @Entity     @Indices({         @Index(members = {"children.name"}),         @Index(members = {"children.age"})     })     static class Parent
19

ObjectDB 2.7.2_x Doctor Yields "Index Requires Rebuild" Always

on it. See indexing errors reported. Run ObjectDB 2.7.1 on same .odb and you will not see indexing errors. Run ... will still show indexing errors when ObjectDB 2.7.2 (or later) Doctor is run on the "repaired" database. Automatic index rebuilding ("<index-update enabled="true" priority="40" />") does not correct

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support