ObjectDB Database Search
1-50 of 200 resultsJPA Criteria API Queries The JPA Criteria API provides an alternative way for defining JPA queries, which is mainly useful for building dynamic queries whose exact structure is only known at runtime. JPA Criteria API vs ... of using the criteria API is that errors can be detected earlier, during compilation | |
SELECT clause (JPQL / Criteria API) of the query result list and other factors. SELECT in Criteria Queries The criteria query API   ... ;(overriding previously set SELECT content if any). Every valid criteria API expression can be used as selection, because all the criteria API expressions are represented by a sub interface | |
Paths and Types in JPQL and Criteria API are considered as one group, and COUNT calculates its size). Criteria Query Paths and Types Paths and navigations are represented in the JPA Criteria API by the Path interface and by ... . For example, the following criteria expression checks if the type of a specified entity e is not  | |
ORDER BY clause (JPQL / Criteria API) can be built using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class ... Criteria Queries The CriteriaQuery interface provides methods for setting the ORDER BY clause ... (c. get ("population"))); Unlike other methods for setting criteria query clauses - the orderBy | |
WHERE clause (JPQL / Criteria API) can be built by using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class ... but they are especially dominant in the WHERE clause. WHERE in Criteria Queries The CriteriaQuery interface provides | |
FROM clause (JPQL / Criteria API). Therefore, ABS, abs, Abs and aBs are all invalid variable names. FROM and JOIN in Criteria Queries FROM query identification variables are represented in criteria queries by sub interfaces of From : Range ... (and its sub interfaces). Criteria Query Roots The CriteriaQuery 's from method serves as a factory | |
Logical Operators in JPQL and Criteria API Logical operators in JPQL and in JPA criteria queries enable composition of complex JPQL boolean ... part of its JDO support. Criteria Query Logical Operators Boolean Expressions and Predicates Boolean expressions are represented in criteria queries by Expression and descendant interfaces. For example | |
Comparison in JPQL and Criteria APIExplains how comparison operators can be used in JPQL queries, including in comparing null values. | |
JPA Metamodel API: The JPA Metamodel API may optionally be used with the JPA Criteria API . Many of the interfaces ... The JPA Metamodel API , which is introduced in JPA 2.0, enables examining the classes, fields and properties of the persistent object model, similarly to the Java reflection API . The main interface | |
JPA Query API variant is valid because it introduces the Country class to ObjectDB. Dynamic JPQL, Criteria API ... can be built dynamically at runtime. The JPA Criteria API provides an alternative way for building dynamic | |
Criteria Query Selection and Results The JPA Criteria API interfaces in this group are used for setting the SELECT and ORDER BY clauses ... clause in a criteria query is represented by Selection : Because Selection is a super interface of Expression , any criteria expression can be used as the SELECT clause content. Multiple | |
Chapter 4 - JPA Queries (JPQL / Criteria) well as how to use the JPA Criteria API , which provides an alternative way for building queries in JPA, based on JPQL. The first section describes the API that JPA provides for using dynamic and static ... (and a criteria query) is explained by describing the main clauses of JPQL queries (SELECT, FROM, WHERE, GROUP | |
What is the Java Persistence API (JPA)? The Java Persistence API (JPA) is a standard API for accessing databases from within Java applications. The main advantage of JPA over JDBC (the older Java API for interacting with databases ... of the Java Persistence API (JPA). By interacting with ObjectDB using standard JPA | |
JPA Metamodel API The JPA Metamodel API provides the ability to examine the persistent object model and retrieve ... Metamodel API is Metamodel . It can be obtained either by the EntityManagerFactory 's getMetamodel ... the specified type to ObjectDB. Type Interface Hierarchy Types are represented in the Metamodel API by | |
JPA Metamodel API Attributes The following interfaces and enum types represent attributes (persistent fields and properties) in the JPA Metamodel API : See the Metamodel Attribute Interface Hierarchy section for more details and examples. | |
JPA Metamodel API Types The following interfaces and enum represent types in the JPA Metamodel API : See the Metamodel Type Interface Hierarchy section for more details and examples. | |
ObjectDB API ReferenceAll about ObjectDB API Reference in Java/JPA database - explanations, examples, references, links and related information. | |
ObjectDB APIsAll about ObjectDB APIs in Java/JPA database - explanations, examples, references, links and related information. | |
JPA Queries;(e.g. "SELECT c FROM Country" ). Criteria Query API Building dynamic queries with a structure ... a TypedQuery or a Query instance. Building a dynamic query using the criteria API is managed by the  ... interface for using the criteria API is the CriteriaBuilder interface: A CriteriaBuilder instance | |
Query Parameters in JPA explicitly (except when using criteria API ), so query parameters are defined implicitly by ... that is built by using the JPA Criteria API - parameters (as other query elements) are represented by objects ... is designated for setting a parameter in a Criteria API query. The reason for having nine set methods | |
JPA Query Expressions (JPQL / Criteria) Query expressions are the foundations on which JPQL and criteria queries are built. Every query ... of JPQL / Criteria query expressions. Atomic Expressions The atomic query expressions are: JPQL / Criteria Variables JPQL / Criteria Parameters JPQL / Criteria Literals Every query expression consists | |
JPA Query Structure (JPQL / Criteria) criteria query clauses are provided as follows: Criteria SELECT ( select , distinct , multiselect , array , tuple , construct ). Criteria FROM ( from , join , fetch ). Criteria WHERE ( where ). Criteria GROUP BY / HAVING ( groupBy , having , count , sum , avg , min , max | |
Criteria Query From Elements The interfaces in this group are in use for setting a criteria query FROM clause. Criteria Query ... variables are represented in criteria queries by descendant interfaces of the From interface: Range ... and its descendant interfaces: See the FROM in Criteria Queries section for more details | |
Strings in JPQL and Criteria Queries expressions (which are more powerful than the LIKE operator). Criteria Query String Expressions JPQL string operators and functions (which are described above) are available also as JPA criteria query ... order to support optional arguments and when applicable simple Java objects as well as criteria expressions. | |
Numbers in JPQL and Criteria Queries. Criteria Query Arithmetic Expressions JPQL arithmetic operators and functions (which are described above) are available also as JPA criteria query expressions. The CriteriaBuilder interface provides ... must be a criteria numeric expression. The other operand may be either another numeric expression or a simple | |
Date and Time in JPQL and Criteria Queries to 0 . Date and Time in Criteria Queries The CriteriaBuilder interface provides three factory methods ... and time parts are also available in criteria queries by using the generic CriteriaBuilder 's function | |
Collections in JPQL and Criteria Queries are treated as synonyms. Criteria Query Collection Expressions JPQL collection operators and functions (which are described above) are available also as JPA criteria query expressions | |
ObjectDB Object Database Features Criteria Query API . Static definition ( named queries ) in annotations (@NamedQuery) and XML. Query ... support of the JPA and JDO APIs . Fundamental features of relational databases (e.g. primary keys ... database files (the ObjectDB Doctor ). Standard Persistence APIs ObjectDB is the only Object-Oriented | |
Criteria Query Expressions The following interfaces are in use in representing general expressions in criteria queries: See the Query Expressions section for more details and examples. | |
Literals in JPQL and Criteria Queries. Criteria Query Literals The CriteriaBuilder interface provides two factory methods for building literal | |
jakarta.persistence.criteria.CriteriaQuery. Since: Jakarta Persistence (JPA) 2.0 The JPA Criteria API Queries article explains how to use ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .CriteriaQuery Type Parameters ... on the specification of the type of the criteria query object created as well as the arguments to the multiselect | |
jakarta.persistence.criteria.CriteriaBuilder compatible with varags. Since: Jakarta Persistence (JPA) 2.0 The JPA Criteria API Queries article ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .CriteriaBuilder Used to construct criteria queries, compound selections, expressions, predicates, orderings. Note that Predicate | |
jakarta.persistence.criteria.CriteriaUpdate The CriteriaUpdate interface defines functionality for performing bulk update operations using the Criteria API . Criteria API bulk update operations map directly to database update operations, bypassing any ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .CriteriaUpdate Type Parameters | |
jakarta.persistence.criteria.CriteriaDelete The CriteriaDelete interface defines functionality for performing bulk delete operations using the Criteria API Criteria API bulk delete operations map directly to database delete operations. The persistence ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .CriteriaDelete Type Parameters | |
jakarta.persistence.criteria.Path. Since: Jakarta Persistence (JPA) 2.0 The Paths and Types in JPQL and Criteria API article explains ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .Path Type Parameters: - the type ... the string-based API may need to specify the type resulting from the get operation in order to avoid | |
jakarta.persistence.criteria.Root Persistence (JPA) 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Root ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .Root Type Parameters ... attribute. Note: Applications using the string-based API may need to specify the type resulting from | |
jakarta.persistence.criteria.Join Persistence (JPA) 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Join . Public ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .Join Type Parameters ... attribute. Note: Applications using the string-based API may need to specify the type resulting from | |
jakarta.persistence.criteria.Predicate. Since: Jakarta Persistence (JPA) 2.0 The Logical Operators in JPQL and Criteria API article explains ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .Predicate Super Interfaces: Expression , Selection , TupleElement The type of a simple or compound predicate: a conjunction or | |
jakarta.persistence.criteria.Order Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .Order An object that defines an ordering over the query results. Since: Jakarta Persistence (JPA) 2.0 The ORDER BY clause (JPQL / Criteria API ) article explains how to use Order . Public Instance Methods Expression getExpression | |
jakarta.persistence.criteria.Selection / Criteria API ) article explains how to use Selection . Public Instance Methods Selection alias ... Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .Selection Type Parameters: - the type of the selection item Super Interfaces: TupleElement The Selection interface defines an item | |
jakarta.persistence.criteria.PluralJoin Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .PluralJoin Type Parameters: - the source type - the element type of the collection - the collection type Super Interfaces: Join ... the string-based API may need to specify the type resulting from the Path.get operation in order | |
jakarta.persistence.criteria.MapJoin Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .MapJoin Type Parameters: - the source type of the join - the type of the target Map value - the type of the target Map key Super ... -based API may need to specify the type resulting from the Path.get operation in order to avoid | |
jakarta.persistence.criteria.SetJoin Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .SetJoin Type Parameters: - the source type of the join - the element type of the target Set Super Interfaces: PluralJoin , Join ... the string-based API may need to specify the type resulting from the Path.get operation in order to avoid | |
jakarta.persistence.criteria.CollectionJoin Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .CollectionJoin Type Parameters: - the source type of the join - the element type of the target Collection Super Interfaces ... : Applications using the string-based API may need to specify the type resulting from the Path | |
jakarta.persistence.criteria.ListJoin Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .ListJoin Type Parameters: - the source type of the join - the element type of the target List Super Interfaces: PluralJoin , Join ... the string-based API may need to specify the type resulting from the Path.get operation in order | |
jakarta.persistence.criteria.From Jakarta Persistence (JPA) Interface jakarta.persistence. criteria .From Type Parameters: - the source type - the target type Super Interfaces: Path , FetchParent , Expression , Selection ... ) Create a path corresponding to the referenced attribute. Note: Applications using the string-based API | |
GROUP BY and HAVING clauses using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class); Root c = q ... and HAVING in Criteria Queries The CriteriaQuery interface provides methods for setting the GROUP BY | |
jakarta.persistence.criteria.Path.get(String) Jakarta Persistence (JPA) Method in jakarta.persistence. criteria .Path Path get ( String attributeName ) Create a path corresponding to the referenced attribute. Note: Applications using the string-based API may need to specify the type resulting from the Path.get operation in order | |
jakarta.persistence.criteria.CriteriaQuery.select(Selection) Jakarta Persistence (JPA) Method in jakarta.persistence. criteria .CriteriaQuery CriteriaQuery select ( Selection selection ) Specify the item that is to be returned in the query result ... API may need to specify the type of the select item when it results from a get or join operation | |
Which API should I use - JPA or JDO? You can use ObjectDB with either the Java Persistence API (JPA) or the Java Data Objects (JDO) API ... the primary API , and if necessary, switch to JDO as a secondary API for special additional features that are supported only by JDO. Selecting the more popular API leads to more portable application |