ObjectDB Database Search
51-100 of 200 resultsjakarta.persistence.Query.setParameter(Parameter,T) Jakarta Persistence (JPA) Method in jakarta.persistence. Query Query setParameter (   ... - parameter object value - parameter value Returns: the same query instance. Throws: IllegalArgumentException - if the parameter does not correspond to a parameter of the query . Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.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 groups query results. A JPQL query with a GROUP BY clause returns properties of the resulting groups instead of individual objects and fields. In the query execution order ... . When a query includes a GROUP BY clause, the database objects (or tuples) that result from the FROM clause | |
ObjectDB Object Database Features, derived attributes, grouping queries and aggregate queries ) which are usually missing from Object Oriented ... entity data cache (per EntityManagerFactory). Database file page cache . Query program cache (for repeating queries with different arguments). Query result cache (for repeating queries | |
Database Explorer it to view data, execute JPQL and JDOQL queries , and edit database content. Running the Explorer ... (entity and embeddable classes) in the database and their persistent fields and indexes. The Query window lets you run JPQL and JDOQL queries , as discussed later. Closing a database connection To close | |
WHERE clause (JPQL / Criteria API) for retrieving a specific subset of objects from the database. How a WHERE clause works The following query ... FROM Country c WHERE c.population :p The FROM clause of this query defines an iteration ... to the SELECT clause to be collected as query results, the WHERE clause acts as a filter. The boolean | |
ORDER BY clause (JPQL / Criteria API) The ORDER BY clause specifies the order for the query results. Any JPQL query that does not ... expressions The following query returns the names of countries with a population of at least one million ... If a query includes an ORDER BY clause, it is the last clause to be executed. The FROM clause first | |
JPA Runtime Tuning & Configuration dynamic options that control runtime behavior and allow you to adjust settings per session, query , or ... every operation in that session. Query (definition): Settings applied to a Query object override session defaults for that query . Operation (argument): Settings passed to specific EntityManager operations ( find | |
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 | |
JPA Criteria FROM and JOIN clause of a query . These interfaces define query variables, including entity roots and various join types ... is structured as follows: Criteria Query From Components in Jakarta Persistence (JPA) 3.2 Criteria query variables The FORM clause in queries defines query variables, which act as loop | |
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. For debugging query failures, you might need to record "all" operations to reproduce ... can use the new indexes to accelerate relevant queries . The element The element specifies settings for the two query cache mechanisms that ObjectDB manages: The results attribute specifies the size | |
Paths and Types in JPQL and Criteria API numbers, booleans, strings, and dates. Values of simple types are more useful in queries ... private, which is usually the case. Navigation through a NULL value The following query retrieves country ... variables) is skipped. To better understand how this works, consider the equivalent JOIN query | |
JPA Entity Fields an automatic query when the entity is retrieved. Note : Navigation through inverse fields is much less efficient than navigation through ordinary persistent fields because it requires running queries ... the following query , where :d represents the Department entity: SELECT e FROM Employee e WHERE e.department | |
Retrieving JPA Entities its persistence context, it returns the existing managed object without querying the database. Otherwise, JPA ... , getReference might return a hollow object instead of querying the database immediately. It never returns null ... an entity and another for checking a persistent field of an entity. Retrieval by query The Query | |
Index Definition Querying without indexes requires sequential iteration over entities in the database. If many ... this full iteration, allowing complex queries over millions of objects to execute quickly ... lastName; Address address; : } Indexes in queries ObjectDB manages a B-tree for every index. A B-tree | |
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 JPA criteria queries combine simple Boolean expressions to form ... , while Java uses its own notation, which is also used by the JDO Query Language (JDOQL). ObjectDB supports both notations. Binary AND (&&) operator The following query retrieves countries whose population | |
Online Backup You can start an online backup by executing a special query on an EntityManager ( em ) instance ... ").getSingleResult(); The backup query string is always "objectdb backup" . The backup is created in the backup ... a custom backup root directory by setting the target parameter before you execute the backup query | |
JPA Exceptions locking wait times. Query exceptions Exceptions specific to query execution and result retrieval: Thrown by Query .getSingleResult() when the query returns no results. Thrown by Query .getSingleResult() when the query returns more than one result. Thrown when a query exceeds the specified timeout limit | |
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 | |
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. | |
Updating JPA Entities and provide better support for automatic change tracking. UPDATE queries UPDATE queries provide an alternative way to update entities in the database. Using an UPDATE query is useful, especially when you must modify many entities in a single operation. The UPDATE Queries in JPA/JPQL section in Chapter 4 explains how to use JPA UPDATE queries . | |
JPA Extended API Reference Guide, query facilities, metamodel details, configuration options, annotations, and exception information ... the fundamental classes and interfaces for entity management and persistence operations. Covers the query API, criteria queries , and JPQL for data retrieval and manipulation. Describes the metamodel and graph APIs | |
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 | |
JPA Shared (L2) Entity Cache several server-side caches: Cache of database file pages . Cache of query programs . Cache of query execution ... for a specific retrieval operation: // Before executing a query : query . setHint ("jakarta.persistence.cache | |
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 | |
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 entities. We will use a simple JPQL query that retrieves points with x value in ... and paste to enter the above query and click Finish . When the data set is created successfully |