About results

11-20 of 200Refresh
Manual
50

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
Manual
27

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
Manual
27

Running JPA Queries [2011-09-21]

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 ... result objects are expected, the query should be run using the getResultList method: TypedQuery
Manual
27

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 ... result objects are expected, the query should be run using the getResultList method: TypedQuery
Forum
22

java.lang.ClassCastException in query results

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

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 a hint "objectdb.result-fetch" set to "LAZY". Another option is to use a report query, i.e
Forum
21

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

CriteriaBuilder to JPQL or from Entity to Primitive. What´s now? This could be the result of getting query results from the cache. There is no difference between criteria queries and string based JPQL queries ... and may result in not being seen by queries: "Updating entity objects in the database using an UPDATE query
Issue
21

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
Forum
21

Empty query results after JAR creation

.jar", I get either empty results or on some cases a "NoResultException" which appears to report ... but once the Jar File is created and moved to a different folder, the query does not return any results any ... file that can be distributed? Thanks for any help.   Empty results or NoResultException may be caused
Issue
21

Query execution creates a wrong result

Hello, we analysed an unexpected behavior and find out that the result of an Query are wrong ... returns an expected result (one Entity). The second Query is the first Query with an additional WHERE condition. But than we get another (wrong) result.   We used Version 2.6.5 and the BUG is fixed