ObjectDB ObjectDB

Internal Website Search

81-90 of 200 resultsRefresh

composite index not used in query

used, query plan: Step 1: Process Action (a) instances ------------------------------------ [Step 1a] Scan index com.agile.hummingbird.Action[startDate] locating all the Action (a) instances. [Step 1b] Filter the results of step 1a retaining only results that satisfy: (a.startDate>:1

Performance issue in a query due to compareTo calls

WHERE v.step.stepNumber = ? is very slow in comparing to the query: SELECT v FROM Values v WHERE v ... , cascade = CascadeType.REMOVE) private Values valuesRef; } @Index (members = {"step.stepNumber ... private long stepNumber; @OneToOne (fetch = FetchType.EAGER) private TCStep step

Slow searching with two indexes

the results of step 1 by: desc(any(any(this.id))). [Step 3] Apply selection and prepare final ... == :r order by id desc Query Plan Description ====================== [Step 1] Scan index com ... the results of step 2 by: desc(this.id). [Step 4] Apply selection and prepare final results

Performance in large transactions

PerformanceTest (and test1_OneTransaction and test2_ManyTransactions), mentioned in step 3, are not ... TransactionsPerformance { static int steps = 10000; public static void main(String[] args) {   test ... myEntity = new MyEntity();   myEntity = em.merge(myEntity);   for (int m = 0; m < steps; m

Issue with UPPER ?

====================== Step 1: Process Mitglied ($1) instances --------------------------------------- [Step 1a ... ($1) instances. [Step 1b] Evaluate fields in Mitglied ($1) instances. Step 2: Process IndividualProfile ($3) instances   (for every result of step 1

JPA Query Structure (JPQL / Criteria)

of up to 6 clauses in the following format: SELECT ... FROM ... [WHERE ...] [GROUP BY ... [HAVING ...]] [ORDER BY ...] The first two clauses, SELECT and FROM are required in every retrieval query (update and delete queries have a slightly different form). The other JPQL clauses, WHERE, GROUP BY

Chapter 4 - JPA Queries (JPQL / Criteria)

(and a criteria query) is explained by describing the main clauses of JPQL queries (SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY): Then the expressions that are used for building JPQL and criteria query

Getting Started with JPA and NetBeans

might look slightly different but the code would be the same). This tutorial consists of the following steps:

Getting Started with JPA and Eclipse

boxes and menus might look slightly different but the code would be the same). This tutorial consists of the following steps:

Report Generation with BIRT and JPA

the BIRT report using a chart and a table: The tutorial consists of the following steps:

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