About result

11-20 of 200Refresh
JPA Doc
48

when(condition, result)

Method javax.persistence.criteria.CriteriaBuilder.SimpleCase SimpleCase when(   C condition,   Expression result ) Add a when/then clause to the case expression. Parameters: condition - "when" condition result - "then" result expression Returns: simple case expression Since: JPA 2.0
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

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
21

ORDER BY clause (JPQL / Criteria API)

The ORDER BY clause specifies a required order for the query results. Any JPQL query that does not include an ORDER BY clause produces results in an undefined and non-deterministic order. ORDER BY ... clause produces objects for examination and the WHERE clause selects which objects to collect as results
Manual
20

CRUD Database Operations with JPA

. The getSingleResult method executes the query and returns the result. It should only be used when exactly one result value is expected (a single Long object in the query above). Let's see another example of a query that returns a single result: Query q2 = em.createQuery("SELECT AVG(p.x) FROM Point p
Manual
18

FROM clause (JPQL / Criteria API)

pair of countries that do not share a border, returning as results only neighbor countries. Caution ... ) is not part of any iterated pair and is therefore excluded from the query results. INNER JOIN simply ... could also cause performance problems. For example, let's look at the following query execution and result
Forum
16

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
JDO Doc
16

javax.jdo.Query

. There are three required elements in a Query: the class of the results, the candidate collection ... , import statements, ordering and grouping specifications, result and result class, the range of results, and flags indicating whether the query result is unique and whether the query can be modified
Forum
16

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
16

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