ObjectDB Database Search
1-50 of 172 resultsjakarta.persistence.criteria.Root Jakarta Persistence (JPA) Interface jakarta.persistence.criteria. Root Type Parameters: - the entity type referenced by the root Super Interfaces: From , Path , FetchParent , Expression , Selection , TupleElement A root type in the from clause. Query roots always reference entities. Since: Jakarta | |
jakarta.persistence.criteria.CriteriaBuilder.treat(Root,Class) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Root treat ( Root root , Class type ) Downcast Root object to the specified type. Parameters: type - type to be downcast to root - root Returns: Root object of the specified type. Since: Jakarta Persistence (JPA) 2.1 | |
jakarta.persistence.criteria.Subquery.correlate(Root) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.Subquery Root correlate ( Root parentRoot ) Create a subquery root correlated to a root of the enclosing query. Parameters: parentRoot - a root of the containing query Returns: subquery root . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.Root.getModel() Jakarta Persistence (JPA) Method in jakarta.persistence.criteria. Root EntityType getModel() Return the metamodel entity corresponding to the root . Returns: metamodel entity corresponding to the root . Since: Jakarta Persistence (JPA) 1.0 | |
FROM clause (JPQL / Criteria API) variable that serves as a root and additional join variables that are bound to path expressions ... variables are represented by the Root interface. Join variables are represented by the Join interface (and its sub interfaces). Criteria Query Roots The CriteriaQuery 's from method serves as a factory | |
Low performance when getting grove roots Hi, I have a grove-like structure of objects, every objects referencing its parent. Root objects have null as the value of this parent reference. To find the roots I execute a query. If the number of objects in the tree is significant, this query takes almost forever, it seems ObjectDB loads | |
Paths and Types in JPQL and Criteria API its subinterfaces ( From , Root , Join and Join 's descendants). Path Expressions The Root and Join interfaces ... Variable Paths: Root country = query. from (Country.class); Join neighborCountry = country. join ... ( Root , Join ) - The creation of a FROM expression automatically modifies the query by adding | |
SELECT clause (JPQL / Criteria API).class); Root c = q. from (Country.class); q. select (c. get ("currency")). distinct (true ... . createQuery (Object[].class); Root c = q. from (Country.class); q. select (cb. array (c. get ("name ... = cb. createTupleQuery (); Root c = q. from (Country.class); q. select (cb. t uple (c. get ("name"), c | |
Online Backup "objectdb backup" . The backup is created under the backup root directory, which by default ... that reflects the current date and time (e.g. 201912312359 ) is created under the backup root ... (if c:\objectdb is the ObjectDB home directory). Custom Backup Target A custom backup root | |
JPA Criteria API Queries); Root c = q. from (Country.class); q. select (c); The CriteriaBuilder interface serves as the main ... for representing the built query. Then a Root instance is created to define a range variable in the FROM ... = cb. createQuery (Country.class); Root c = q. from (Country.class); ParameterExpression p = cb | |
Database Replication and Clustering databases on the slave server are automatically generated under a special root directory, $replication , under the server data root directory. Starting a new replication of an existing master database | |
jakarta.persistence.criteria.Subquery of the given basic type. Since: Jakarta Persistence (JPA) 3.2 Root correlate ( Root parentRoot ) Create a subquery root correlated to a root of the enclosing query. Parameters: parentRoot - a root of the containing query Returns: subquery root . Since: Jakarta Persistence (JPA) 1.0 Join correlate ( Join | |
jakarta.persistence.criteria.AbstractQuery directly in query construction. All queries must have: a set of root entities (which may in turn ... Persistence (JPA) 1.0 Root from ( Class entityClass ) Create and add a query root corresponding to the given entity, forming a cartesian product with any existing roots . Parameters: entityClass - the entity | |
jakarta.persistence.criteria.CriteriaQuery.. Since: Jakarta Persistence (JPA) 1.0 Root from ( Class entityClass ) Create and add a query root corresponding to the given entity, forming a cartesian product with any existing roots . Inherited from AbstractQuery Parameters: entityClass - the entity class Returns: query root corresponding | |
jakarta.persistence.criteria.CriteriaUpdate. A CriteriaUpdate object must have a single root . Since: Jakarta Persistence (JPA) 2.1 Public Instance Methods Root from ( Class entityClass ) Create and add a query root corresponding to the entity that is the target of the update. A CriteriaUpdate object has a single root , the entity | |
jakarta.persistence.criteria.CriteriaDelete must have a single root . Since: Jakarta Persistence (JPA) 2.1 Public Instance Methods Root from ( Class entityClass ) Create and add a query root corresponding to the entity that is the target of the DELETE. A CriteriaDelete object has a single root , the entity that is being deleted. Parameters: entityClass | |
Server Configuration to the document root directory of a web server. Every database file in the data directory and in | |
Numbers in JPQL and Criteria Queries;function returns a long value). The SQRT Function The SQRT function returns the square root | |
WHERE clause (JPQL / Criteria API)); Root c = q. from (Country.class); q. select (c); ParameterExpression p = cb. parameter (Integer | |
Database Connection using JPA, relative to the server data root path. Connection URL Parameters The following parameters | |
Chapter 6 - Configuration The ObjectDB configuration file contains one root element with seven subelements: ... ... ... ... ... ... ... Each one of these seven configuration elements is explained in a separate section: This page explains how ObjectDB configuration works in general. The Configuration Path By default | |
GROUP BY and HAVING clauses using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class); Root c = q | |
JPA Persistence Unit packed in a JAR yet, ObjectDB (as an extension) automatically registers classes under the classpath root | |
Server User List path attribute specifies a directory path relative to the root data directory. Permission to access | |
ORDER BY clause (JPQL / Criteria API)); Root c = q. from (Country.class); q. select (c); q. orderBy (cb. asc (c. get ("currency")), cb. desc | |
Criteria Query From Elements variables (bound by an entity class) are represented by the Root subinterface: Join variables (bound by | |
JPA Exceptions.TransactionRequiredException Exception Class Overview The root of the JPA exception class subtree is: General errors | |
jakarta.persistence.criteria.CriteriaBuilder ( Expression x ) Create an expression that returns the square root of its argument. Parameters: x - expression Returns: square root . Since: Jakarta Persistence (JPA) 1.0 Expression substring ... of the specified type. Since: Jakarta Persistence (JPA) 2.1 Root treat ( Root root , Class type ) Downcast | |
jakarta.persistence.NamedEntityGraph to the root entity of the graph, and specifies the limits of the graph of associated attributes and entities fetched when an operation which retrieves an instance or instances of the root entity is executed ... . If no name is explicitly specified, the name defaults to the entity name of the annotated root | |
jakarta.persistence.EntityGraph Jakarta Persistence (JPA) Interface jakarta.persistence.EntityGraph Type Parameters: - The type of the root entity. Super Interfaces: Graph This type represents the root of an entity graph ... and entity relationships. The root must be an entity type. The methods to add subgraphs implicitly create | |
jakarta.persistence.criteria.AbstractQuery.getRoots()() Return the query roots . These are the roots that are defined for the CriteriaQuery or Subquery itself, including any subquery roots defined as a result of correlation. Returns an empty set if no roots have been defined. Modifications to the set do not affect the query. Returns: the set of query roots . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.AbstractQuery.from(Class) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.AbstractQuery Root from ( Class entityClass ) Create and add a query root corresponding to the given entity, forming a cartesian product with any existing roots . Parameters: entityClass - the entity class Returns: query | |
jakarta.persistence.criteria.AbstractQuery.from(EntityType) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.AbstractQuery Root from ( EntityType entity ) Create and add a query root corresponding to the given entity, forming a cartesian product with any existing roots . Parameters: entity - metamodel entity representing | |
jakarta.persistence.criteria.CriteriaUpdate.from(Class) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaUpdate Root from ( Class entityClass ) Create and add a query root corresponding to the entity that is the target of the update. A CriteriaUpdate object has a single root , the entity that is being updated | |
jakarta.persistence.criteria.CriteriaUpdate.from(EntityType) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaUpdate Root from ( EntityType entity ) Create and add a query root corresponding to the entity that is the target of the update. A CriteriaUpdate object has a single root , the entity that is being updated | |
jakarta.persistence.criteria.CriteriaDelete.from(Class) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaDelete Root from ( Class entityClass ) Create and add a query root corresponding to the entity that is the target of the DELETE. A CriteriaDelete object has a single root , the entity that is being deleted | |
jakarta.persistence.criteria.CriteriaDelete.from(EntityType) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaDelete Root from ( EntityType entity ) Create and add a query root corresponding to the entity that is the target of the DELETE. A CriteriaDelete object has a single root , the entity that is being deleted | |
jakarta.persistence.criteria.PluralJoin to avoid the use of Path variables. For example: CriteriaQuery q = cb.createQuery(Person.class); Root p ... "))); rather than: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from(Person.class); Path nicknames = p | |
jakarta.persistence.criteria.Path the use of Path variables. For example: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from ... q = cb.createQuery(Person.class); Root p = q.from(Person.class); Path nicknames = p.get("nicknames | |
jakarta.persistence.criteria.MapJoin the use of Path variables. For example: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from ... q = cb.createQuery(Person.class); Root p = q.from(Person.class); Path nicknames = p.get("nicknames | |
jakarta.persistence.criteria.SetJoin the use of Path variables. For example: CriteriaQuery q = cb.createQuery(Person.class); Root p = q ... "))); rather than: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from(Person.class); Path nicknames = p | |
jakarta.persistence.criteria.CollectionJoin(Person.class); Root p = q.from(Person.class); q.select(p) .where(cb.isMember("joe", p.get("nicknames"))); rather than: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from(Person.class | |
jakarta.persistence.criteria.ListJoin to avoid the use of Path variables. For example: CriteriaQuery q = cb.createQuery(Person.class); Root p = q ... "))); rather than: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from(Person.class); Path nicknames = p | |
jakarta.persistence.criteria.From of Path variables. For example: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from(Person ... .createQuery(Person.class); Root p = q.from(Person.class); Path nicknames = p.get("nicknames"); q | |
jakarta.persistence.criteria.Join.createQuery(Person.class); Root p = q.from(Person.class); q.select(p) .where(cb.isMember("joe", p.get("nicknames"))); rather than: CriteriaQuery q = cb.createQuery(Person.class); Root p = q.from(Person | |
jakarta.persistence.criteria.CriteriaUpdate.getRoot() Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaUpdate Root getRoot() Return the query root . Returns: the query root . Since: Jakarta Persistence (JPA) 1.0 | |
Java EE 6 JPA Tutorial - Eclipse Project the guestbook-jee6 directory as Root Directory and press ENTER . Select the project and click | |
Spring MVC JPA Tutorial - Eclipse Project-spring directory as Root Directory and press ENTER . Select the project and click Finish | |
JPA Web App Tutorial - Eclipse Project; guestbook-web directory as Root Directory and press ENTER . Select the project and click Finish | |
Getting Started with JPA - Eclipse Project directory as Root Directory and press ENTER . Select the project and click Finish . Run the project in |