35 | FROM clause (JPQL / Criteria API) capital) is not part of any iterated pair and is therefore excluded from the query results. INNER JOIN ... and result iteration: TypedQuery<Country> query = em.createQuery("SELECT c FROM Country c", Country.class); List<Country> results = query.getResultList(); for (Country c : results |
35 | javax.persistence.Query back Since: JPA 1.0 int getFirstResult() The position of the first result the query object was set to retrieve. The position of the first result the query object was set to retrieve. Returns 0 if setFirstResult was not applied to the query object. Returns: position of the first result Since: JPA 2 |
34 | Collections in JPQL and Criteria QueriesCollections may appear in JPQL queries: as parameters - when collections are assigned as arguments ... , which should be used for checking other collections, such as a collection that is passed to the query ... of collection, so in ObjectDB these operators are treated as synonyms. Criteria Query Collection |
34 | Literals in JPQL and Criteria Queries literals should be used sparingly as queries that use parameters instead of literals ... values. Literals should only be embedded in JPQL queries when a single constant value is always used ... support for enum literals. Enum literals in JPQL queries use the ordinary Java syntax for enum |
34 | JPA Annotations for JPQL QueriesThe following annotations are used to define static named JPA queries: The JPA Named Queries section of the ObjectDB Manual explains and demonstrates how to use these annotations to define named JPQL queries. |
33 | Criteria Query ExpressionsThe following interfaces are in use in representing general expressions in criteria queries: See the Query Expressions section for more details and examples. |
33 | JPA Annotations for SQL QueriesThe following JPA annotations are designated for SQL queries on relational databases: ObjectDB supports only the preferred JPA query language, JPQL, and silently ignores all the above annotations. |
30 | 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 |
29 | ORDER BY clause (JPQL / Criteria API)The ORDER BY clause specifies a required order for the query results. Any JPQL query that does not ... expressions is vendor dependent. Query results can also be ordered by multiple order expressions. In ... BY clause in the above query orders the results by the currency name. Without an ORDER BY clause |
2 | setResultClass(cls) or set to null, the result class defaults to the candidate class of the query. If the result consists ... argument is the value from the query result. Portable result classes do not invoke any persistence ... Method javax.jdo.Query void setResultClass( Class cls ) Specify the type of object in |
