ObjectDB Database Search

1-50 of 200 results

jakarta.persistence.StoredProcedureQuery.execute()

Jakarta Persistence (JPA) Method in jakarta.persistence.StoredProcedureQuery boolean execute ... result corresponds to result set. Throws: PersistenceException - if the query execution exceeds ... execution exceeds the query timeout value set and only the statement is rolled back. Since: Jakarta Persistence (JPA) 1.0

Attempt to execute a query using a closed EntityManager

. com.objectdb.o.UserException - Attempt to execute a query using a closed EntityManager at com ... and executes the following. 3. First statement: @Stateless ClientC.create(and passes the user) 4 ... to execute a query using a closed EntityManager at org.apache.myfaces.view.facelets.el

Query execution time issue

, and there is only on Entity in the database. Execution of this query (running with ObjectDB) takes about 10-12 seconds. If i remove ANY 5 left joins, query execution time drops to about 50 milliseconds. Adding a new left join on remaining 8 slows down query execution time drastically. Please help

Getting exception while executing the Query

I have facing a problem when i am executing the query first time, Please find the stack trace ... .objectdb.jdo.JdoQuery. execute (JdoQuery.java:720) I am using the following code to execute the same Query ... ()); Collection collection = (Collection)query. execute (); query. execute () is throwing the exception Any

Query Execution on parallel threads don't lead to performance improvements

Hello, we want to execute querys in parallel threads on the same entity type in order to increase ... are fine. A parallel query execution doesn't necessarily improve performance, if the serial execution ... a single query? Not every query can benefit from parallel execution . Regarding the profiling data

Querys slower when execute a query after every persist

The test case of the java file attachment persists many entities and executes a query after every persist. The execution time amounts 2 sec when the test persists 1000 entities. The execution time ... more time (i.e. every query execution requires a more expensive flush). Results of your test

Debuging query before execution

Hi, Is is possible in any way to get string representation of a query right before execution , after setting parameters? Of course it's easy to print out query string when we build it by concatenating many strings, but even then we miss attributes. lwalkowski Lukasz Walkowski

NullpointerException when execute a merge

.invoke(Method.java:606) at org.eclipse.e4.core.internal.di.MethodRequestor. execute (MethodRequestor.java

Internal objectdb error when execute a flush

We get an internal objectdb error, when we execute a flush. Why? What's wrong? It performs with version objectdb-2.6.4_04. It does not perform with version objectdb-2.6.6_04.   Caused by: com.objectdb.o.InternalException: Unexpected internal exception at com.objectdb.o.JPE.h(JPE.java:168

Database Explorer

it to view data, execute JPQL and JDOQL queries, and edit database content. Running the Explorer The ObjectDB Explorer is packaged in the explorer.jar executable file, which is located in the bin directory ... switches the current viewer to focus on that object. Executing queries The Query window on the left lets

Setting and Tuning of JPA Queries

The Query and TypedQuery interfaces define various methods for setting and tuning query execution ... execution is much more complex. Therefore, before a query is executed , any uncommitted database changes ... the FlushModeType enum, which has two values: AUTO - Flushes changes before query execution

Query Parameters in JPA

Query parameters enable you to define reusable queries. You can execute these queries with different parameter values to retrieve different results. Executing the same query multiple times with different parameter values is more efficient than using a new query string for each execution

JPA Listeners & Callbacks Annotations

entities to the database: Executes before the EntityManager persist operation. This is useful for initializing default values or creation timestamps. Executes after the entity is persisted ... when modifying existing entities and flushing changes to the database: Executes before the database update

FROM clause (JPQL / Criteria API)

objects with two range variables forming nested loops (outer and inner) might prevent query execution ... to optimize the execution of multivariable queries. Whenever possible, full nested iteration over the entire Cartesian product is avoided. For example, the query above can be executed as follows: An outer

JPA Queries

Jakarta Persistence provides powerful APIs for executing database queries using JPQL strings or ... with full type safety. General query objects Execute SELECT, UPDATE and DELETE queries in JPA using these core interfaces: The base interface for executing queries in JPA. It is often replaced by

jakarta.persistence.StoredProcedureQuery

: Query Interface used to control stored procedure query execution . Stored procedure query execution ... and getSingleResult are called on a StoredProcedureQuery object, the provider calls execute ... is called on a StoredProcedureQuery object, the provider will call execute on an unexecuted stored

SELECT clause (JPQL / Criteria API)

results as arrays. The following code demonstrates the execution of the query and iteration ... results. The following code demonstrates the execution of the query and iteration over the results: List ... ). The following code demonstrates the execution of the query: List results = em. createQuery (q

Running JPA Queries

.executeUpdate () : Use to run DELETE and UPDATE queries. Ordinary query execution (with getResultList ... to retrieve only the names instead of the entire Country instances. Single-result query execution ... with caution and be prepared to catch and handle these exceptions. DELETE and UPDATE query execution

JPA Criteria API Queries

, which you can then execute : TypedQuery query = em. createQuery (q); List results = query. getResultList ... can be executed more concisely: TypedQuery query = em. createQuery ("SELECT c FROM Country c", Country.class ... a TypedQuery instance, query execution and settings are similar, regardless of how the 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 ... . If this EntityManager is associated with a transaction, the function is executed in the context of the transaction

JPA Entity Fields

. However, even with an index, executing a query to load a field is relatively slow ... because no proxy class is used and the inverse query is executed eagerly when the entity is first

Date and Time in JPQL and Criteria Queries

when the query is executed : CURRENT_DATE : Returns the current date as a java.sql.Date instance. CURRENT_TIME ... once on the client side, these expressions are re-evaluated on the server each time the query is executed

Index Definition

this full iteration, allowing complex queries over millions of objects to execute quickly ... them to accelerate query execution . Indexes are especially efficient for lookup and range queries: SELECT p

DELETE Queries in JPA/JPQL

is a good practice. As with any operation that modifies the database, DELETE queries must be executed ... DELETE queries are executed using the executeUpdate method: int deletedCount = em. createQuery

What are the main benefits of using ObjectDB?

the execution time of object oriented applications significantly. For instance, collection and map ... convert these queries to SQL and then transition the SQL to the DBMS for execution through a JDBC

JPA Core Types

interface for executing operations that return a value via a JDBC connection. A functional interface for executing void operations via a JDBC connection.

JPA Criteria Queries

to define SELECT, WHERE , GROUP BY , and ORDER BY clauses. To execute the query, pass the instance ... query, a subquery cannot be executed directly; it serves as an expression within the parent query

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

UPDATE SET Queries in JPA/JPQL

database modification, you must execute UPDATE queries within an active transaction. The changes ... : UPDATE Country SET population = 0, area = 0 Execute UPDATE queries by using the executeUpdate

Online Backup

You can start an online backup by executing a special query on an EntityManager ( em ) instance ... a custom backup root directory by setting the target parameter before you execute the backup query

jakarta.persistence.TypedQuery

type Super Interfaces: Query Interface used to control the execution of typed queries ... ) explains how to use TypedQuery . Public Instance Methods int executeUpdate () Execute an update or delete ... query. PersistenceException - if the query execution exceeds the query timeout value set

jakarta.persistence.Query

execution . See Also: TypedQuery StoredProcedureQuery Parameter Since: Jakarta Persistence (JPA) 1.0 ... executeUpdate () Execute an update or delete statement. Returns: the number of entities updated or deleted ... statement or for a criteria query. PersistenceException - if the query execution exceeds the query timeout

Database Management Settings

query programs eliminate the need to recompile queries, but the queries still must be executed

Apache License, Version 2.0, January 2004

the terms of any separate license agreement you may have executed with Licensor regarding

Database Transaction Replayer

is also created in the recording directory. Its name, .odb , specifies the last executed transaction

WHERE clause (JPQL / Criteria API)

, defining appropriate indexes can significantly improve query execution time. WHERE filter in multi

JPA Connections and Transactions

, which are used to execute database queries. Every JPA implementation provides classes that implement

JPA Annotations

specifically for Object-Relational Mapping (ORM) and native SQL execution ; ObjectDB ignores these relational

Paths and Types in JPQL and Criteria API

execution . The constructed variable expression can also be used explicitly in other query clauses

ObjectDB Object Database Features

for efficient reuse of one query in multiple executions . Result range settings (first, max) - for paging

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, the GROUP BY clause is processed after the FROM and WHERE clauses but before the SELECT clause

ORDER BY clause (JPQL / Criteria API)

If a query includes an ORDER BY clause, it is the last clause to be executed . The FROM clause first

JPA Exceptions

locking wait times. Query exceptions Exceptions specific to query execution and result retrieval

Unexpected exception when execute query without enhanced entities

ObjectDB 2.8.7.b08 Our entities are not enhanced and we execute a query "select max(uid) from ModelElementImpl". In the objectdb.conf the reflection is set to error. ...   We got following exception after execution of the query: Caused by: com.objectdb.o.UserException: Unexpected query token

Query Execution Error

')).contracts.active=true)))) results in "Query Execution Error===null" in Explorer and Internal Exception

Sometimes the ObjectDB throws an internal expeption if a persist() was executed

was mistakenly executed on a test machine without ObjectDB lizense. At the beginning of the test

Internal Exception during query execution

execution . Please post the query (and also try it with build 09). support Support Most simple query

Sometimes the ObjectDB throws an internal expeption if a find() was executed

Sometimes the ObjectDB throws an internal exception if a find() was executed . It is a sporadic issue that occurs only with Objectdb 2.7.0_b2 and only if the entites are enhanced. (We don't enabled the new property "objectdb.temp.extended-ref-retrieval" from http://www.objectdb.com/database/forum

Step 6: Run the Java EE 6 Application

You can run the application now by right clicking the  GuestServlet node (in the [Projects] window), selecting  Run File , and then clicking  OK (no need to change the servlet execution URI). Since we are using ObjectDB in embedded mode - the database file is created

Step 6: Run the Web Application

You can run the application now by right clicking the GuestServlet node (in the [Projects] window), selecting Run File , and then clicking  OK (no need to change the servlet execution URI). Since we are using ObjectDB in embedded mode - the database file is created under the Tomcat directory