ObjectDB Database Search
51-100 of 200 resultsjakarta.persistence.Query.setParameter(Parameter,Calendar,TemporalType) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Query setParameter (   ... object value - parameter value Returns: the same query instance. Throws: IllegalArgumentException - if the parameter does not correspond to a parameter of the query . Deprecated: Newly-written code | |
jakarta.persistence.Query.setParameter(Parameter,Date,TemporalType) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Query setParameter (   ... value - parameter value Returns: the same query instance. Throws: IllegalArgumentException - if the parameter does not correspond to a parameter of the query . Deprecated: Newly-written code should use | |
jakarta.persistence.Query.setParameter(String,Object) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Query setParameter (   ... : name - parameter name value - parameter value Returns: the same query instance. Throws: IllegalArgumentException - if the parameter name does not correspond to a parameter of the query or if the argument is of incorrect type. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.getFirstResult() Jakarta Persistence (JPA) Method in jakarta.persistence. Query int getFirstResult() 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: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.NamedQuery.query Jakarta Persistence (JPA) Method in jakarta.persistence.NamedQuery String query (Required) The query string in the Jakarta Persistence query language. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.getParameter(String) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Parameter getParameter (   ... . This method is not required to be supported for native queries . Parameters: name - parameter name Returns: parameter object. Throws: IllegalStateException - if invoked on a native query | |
jakarta.persistence.Query.getFlushMode() Jakarta Persistence (JPA) Method in jakarta.persistence. Query FlushModeType getFlushMode() Get the flush mode in effect for the query execution. If a flush mode has not been set for the query object, returns the flush mode in effect for the entity manager. Returns: flush mode. Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.Query.getParameter(int) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Parameter getParameter (   ... with the given position. This method is not required to be supported for native queries . Parameters ... query when the implementation does not support this use. IllegalArgumentException - if the parameter | |
jakarta.persistence.Query.unwrap(Class) Jakarta Persistence (JPA) Method in jakarta.persistence. Query T unwrap ( Class cls ... implementation of Query does not support the given type, the PersistenceException is thrown ... implementing Query or an interface it implements. Returns: an instance of the specified class. Throws | |
jakarta.persistence.Query.setMaxResults(int) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Query setMaxResults ( int maxResult ) Set the maximum number of results to retrieve. Parameters: maxResult - maximum number of results to retrieve Returns: the same query instance. Throws: IllegalArgumentException | |
jakarta.persistence.Query.setFirstResult(int) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Query setFirstResult ( int startPosition ) Set the position of the first result to retrieve. Parameters: startPosition - position of the first result, numbered from 0 Returns: the same query instance. Throws | |
jakarta.persistence.Query.getHints() Jakarta Persistence (JPA) Method in jakarta.persistence. Query Map getHints() Get the properties and hints and associated values that are in effect for the query instance. Returns: query properties and hints. Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.NamedNativeQuery.query Jakarta Persistence (JPA) Method in jakarta.persistence.NamedNativeQuery String query The native SQL query string. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.getParameterValue(Parameter) Jakarta Persistence (JPA) Method in jakarta.persistence. Query T getParameterValue ( Parameter param ) Return the input value bound to the parameter. (Note that OUT parameters ... - if the parameter has not been bound. IllegalArgumentException - if the parameter is not a parameter of the query . Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.Query.getCacheRetrieveMode() Jakarta Persistence (JPA) Method in jakarta.persistence. Query CacheRetrieveMode getCacheRetrieveMode() The cache retrieval mode that will be in effect during query execution. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.Query.getCacheStoreMode() Jakarta Persistence (JPA) Method in jakarta.persistence. Query CacheStoreMode getCacheStoreMode() The cache storage mode that will be in effect during query execution. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.Query.getTimeout() Jakarta Persistence (JPA) Method in jakarta.persistence. Query Integer getTimeout() The query timeout. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.PersistenceConfiguration.QUERY_TIMEOUT Jakarta Persistence (JPA) Field in jakarta.persistence.PersistenceConfiguration QUERY _TIMEOUT Default query timeout hint. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.QueryTimeoutException.query Jakarta Persistence (JPA) Field in jakarta.persistence.QueryTimeoutException query Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.getParameterValue(String) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Object getParameterValue ( String name ) Return the input value bound to the named parameter. (Note that OUT parameters are unbound.) Parameters: name - parameter name Returns: parameter value. Throws: IllegalStateException | |
jakarta.persistence.Query.getParameterValue(int) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Object getParameterValue ( int position ) Return the input value bound to the positional parameter. (Note that OUT parameters are unbound.) Parameters: position - position Returns: parameter value. Throws | |
jakarta.persistence.Query.isBound(Parameter) Jakarta Persistence (JPA) Method in jakarta.persistence. Query boolean isBound ( Parameter param ) Return a boolean indicating whether a value has been bound to the parameter. Parameters: param - parameter object Returns: boolean indicating whether parameter has been bound. Since: Jakarta Persistence (JPA) 2.0 | |
GROUP BY and HAVING clauses The GROUP BY clause enables grouping of query results. A JPQL query with a GROUP BY clause returns ... clause in the query execution order is after the FROM and WHERE clauses, but before the SELECT clause. When a GROUP BY clause exists in a JPQL query , database objects (or tuples of database objects | |
ObjectDB Object Database Features, derived attributes, grouping queries and aggregate queries ) which are usually missing from Object Oriented ... . Query program cache (for repeating queries with different arguments). Query result cache (for repeating queries with the same arguments). Many other internal caches. Indexing Single field and multi field | |
Database Explorer to view data in ObjectDB databases, execute JPQL and JDOQL queries and edit the content of databases ... and embeddable classes) in the database and their persistent fields and indexes. The [ Query ] window enables running JPQL and JDOQL queries , as discussed below. Closing a Database Connection Use the File Close | |
WHERE clause (JPQL / Criteria API) JPQL query that retrieves selective objects from the database. Out of the four optional clauses of JPQL queries , the WHERE clause is definitely the most frequently used. How a WHERE Clause Works The following query retrieves only countries with a population size above a population size p | |
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 The following query returns names of countries whose population size ... expressions in the SELECT clause are allowed in the ORDER BY clause. The following query , for example | |
jakarta.persistence.StoredProcedureQuery: Query Interface used to control stored procedure query execution. Stored procedure query execution ... on an unexecuted stored procedure query before processing getResultList or getSingleResult . When executeUpdate ... procedure query , followed by getUpdateCount . The results of executeUpdate | |
jakarta.persistence.TypedQuery Jakarta Persistence (JPA) Interface jakarta.persistence.TypedQuery Type Parameters: - query result type Super Interfaces: Query Interface used to control the execution of typed queries . See Also: Query Parameter Since: Jakarta Persistence (JPA) 2.0 Chapter 4 - JPA Queries (JPQL / Criteria | |
Database Management Settings (which modify the database) have to be recorded. For debugging of query failure ... to accelerate the execution of relevant queries . The element The element specifies settings of the two cache mechanisms that ObjectDB manages for queries : The results attribute specifies the size | |
Paths and Types in JPQL and Criteria API, string, date). Simple type values are more useful in queries . They have special operators ... ). Navigation through a NULL value The following query retrieves country names with their capital city names ... the equivalent JOIN query . Entity Type Expressions The TYPE operator (which is new in JPA 2) returns the type | |
JPA Entity Fields after retrieval by a special automatic query . Note : Navigation through inverse fields is much less efficient than navigation through ordinary persistent fields, since it requires running queries . Inverse ... the following query (where :d represents the Department entity): SELECT e FROM Employee e WHERE e | |
Index Definition Querying without indexes requires iteration over entity objects in the database one by ... indexes the iteration can be avoided and complex queries over millions of objects can be executed quickly ... firstName; String lastName; Address address; : } Indexes in Queries ObjectDB manages a BTree | |
Online Backup. Starting Online Backup The online backup can be started by executing a special query on an EntityManager ... ; em.createQuery("objectdb backup").getSingleResult(); The backup query string is always exactly ... directory can be specified by setting the target parameter before executing the backup query :   | |
jakarta.persistence.EntityManager their primary key, and execute queries which range over entity types. An entity may be disassociated from ... must also be flushed before execution of any query whose result set would be affected by unflushed modifications ... accepts LockOption s. See Also: Query TypedQuery CriteriaQuery PersistenceContext | |
Logical Operators in JPQL and Criteria API Logical operators in JPQL and in JPA criteria queries enable composition of complex JPQL boolean ... , the JDO Query Language). ObjectDB supports both forms. Binary AND (&&) Operator The following query retrieves countries whose population and area (both) exceed specified limits: SELECT c FROM | |
jakarta.persistence.criteria.CriteriaQuery , CommonAbstractCriteria The CriteriaQuery interface defines functionality that is specific to top-level queries . Since: Jakarta Persistence (JPA) 2.0 The JPA Criteria API Queries article explains how to use ... query results are eliminated. A true value will cause duplicates to be eliminated. A false value | |
Retrieving JPA Entity Objects and the other for checking a persistent field of an entity object. Retrieval by Query The most flexible method for retrieving objects from the database is to use queries . The official query language of JPA is JPQL (Java Persistence Query Language). It enables retrieval of objects from the database by | |
Is ObjectDB a NoSQL Database? of NoSQL technology, which are weak query capabilities and lack of ACID (atomicity, consistency, isolation, durability). Unlike other NoSQL solutions, ObjectDB provides full support of rich complex queries , using two standard Java query languages: JPQL (Java Persistence Query Language) and JDOQL (JDO | |
Is ObjectDB better than competing object databases? do not support aggregate queries (max, min, count, sum and avg). ObjectDB supports rich queries , including aggregate queries , as part of its support of JPQL (JPA Query Language) and JDOQL (JDO Query Language). ObjectDB is faster than other products. | |
Deleting JPA Entity Objects to automatic removal of that object from the database. DELETE Queries DELETE queries provide an alternative way for removing entity objects from the database. Deleting objects using a DELETE query ... ;The DELETE Queries in JPA/JPQL in chapter 4 explains how to use JPA DELETE queries . | |
Comparison in JPQL and Criteria API Most JPQL queries use at least one comparison operator in their WHERE clause. Comparison Operators ... its own notation (which is also in use by JDOQL, the JDO Query Language). ObjectDB supports both forms ... . Equality operators (=, , == , != ) on strings in queries follow the logic of Java's equals | |
Updating JPA Entity Objects Queries UPDATE queries provide an alternative way of updating entity objects in the database. Modifying objects using an UPDATE query may be useful especially when many entity objects have to be modified in one operation. The UPDATE Queries in JPA/JPQL in chapter 4 explains how to use JPA UPDATE queries . | |
What are the main benefits of using ObjectDB? processes JPQL (JPA Query Language) and JDOQL (JDO Query Language) queries directly, where ORM tools first convert these queries to SQL and then transition the SQL to the DBMS for execution through a JDBC | |
Shared (L2) Entity Cache side: Cache of database file pages . Cache of query programs . Cache of query execution results ... can also be overridden for a specific retrieval operation: // Before executing a query : query . setHint | |
jakarta.persistence.criteria.AbstractQuery functionality that is common to both top-level queries and subqueries. It is not intended to be used directly in query construction. All queries must have: a set of root entities (which may in turn own joins). All queries may have: a conjunction of restrictions. Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.criteria.Subquery 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 parentJoin ) Create a subquery join object correlated to a join object of the enclosing query | |
jakarta.persistence.criteria.CriteriaBuilder criteria queries , compound selections, expressions, predicates, orderings. Note that Predicate ... compatible with varags. Since: Jakarta Persistence (JPA) 2.0 The JPA Criteria API Queries article ... to specify a constructor that is applied to the results of the query execution. If the constructor | |
JPA Persistable Types are represented in queries by entity names . By default, the entity name is the unqualified name ... . their instances cannot be shared by different entity objects and they cannot be queried directly), so a decision ... ). It simplifies queries on dates and ranges of dates. When an entity is stored, its date and time fields | |
Step 4: Create an ObjectDB Data Set Queries against the database are represented in BIRT as data sets. To create the data set: Open ... this tutorial contains Point entity objects. We will use a simple JPQL query that retrieves points with x ... copy and paste to enter the above query and click Finish . When the data set is created |