ObjectDB ObjectDB

Internal Website Search

11-20 of 200 resultsRefresh
101

Query only works correctly when debug printing results

on pc) the query results are only fully read back when debug printing the result contents before closing ... part commented out, the result doesnt contain all the data. The field requirementList is read back as null ... RequirementLevelEntity l", RequirementLevelEntity.class); List results = query.getResultList
101

java.lang.ClassCastException in query results

result : results)" line TypedQuery<Stadium> query = em.createQuery( "SELECT Name, Capacity, City FROM Stadium s", Stadium.class); List<Stadium> results = query.getResultList(); for (Stadium result : results) { System.out.println("Name: " + result.Name + ", Capacity: " + result
100

Iterating over large result set

of given size until whole result set is iterated. What I'm thinking about is some kind of streaming of result set from database without building whole object graph representing fetched data in application ... with one query by running the query with a hint "objectdb.result-fetch" set to "LAZY". Another option is to use
100

Query results are not up to date for entities, not primitives

This could be the result of getting query results from the cache. There is no difference between ... that updates by queries bypass the cache and may result in not being seen by queries: "Updating entity ... queries should return up to date results, if: You are using a new EntityManager (i.e. with no old
99

Unexpected COUNT Results

with size 1380. This is expected result If we add COUNT operator: b. SELECT COUNT($1.id) FROM Pa3DataKey ... .anritsu.pa3") This query returns value 1758. This is not expected result The same issue is seen when performing the query from java code Can you please explain why query results in 1.b and 1.c are not
45

SELECT clause (JPQL / Criteria API)

> results = query.getResultList(); Because the results are managed entity objects they have all the support ... objects, transparent update detection, support for delete, etc. Query results are not limited to entity ... . Specifying the required query results more precisely can improve performance and in some cases
24

Setting and Tuning of JPA Queries

execution if invoked before a query is run using getResultList or getSingleResult. Result Range (setFirstResult, setMaxResults) The setFirstResult and setMaxResults methods enable defining a result window that exposes a portion of a large query result list (hiding anything outside that window
24

Running JPA Queries

when exactly one result object is expected. Query.getResultList - for general use in any other case ... - for use when exactly one result object is expected. TypedQuery.getResultList - for general use in any ... <Country> results = query.getResultList(); Both Query and TypedQuery define a getResultList method
19

DB persist operation results are not available for another Thread/EntityManager immdiately

a query. But there are not any results available. We debugged the problem. Thread B executes the query and prints the results to the console, but there are not results. After that the thread stops ... again. And we get the expected results. Why? It is also possible to insert a Thread.sleep(1000) before executing
4

[ODB1] Chapter 7 - JDOQL Queries

to boost recycling rates in Manchester approved n criteria, and iteration over the results in ... a persistent class) A filter, which is a boolean expression in a Java like syntax The query result ... is 18 or older: Query query = pm.newQuery(Person.class, "this.age >= 18"); Collection result

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