About query

151-160 of 200Refresh
Forum
16

Criteria query error: Unexpected query token

.arquillian.spi.ArquillianProxyException: com.objectdb.o._PersistenceException : Unexpected query token ... It seems that the query is invalid because a SELECT is not specified. Unexpected query token 'FROM' (SELECT is expected) A query with no SELECT may be valid in Hibernate HQL but not in JPQL and JPA Criteria API
Forum
15

ObjectDB Explorer query error: Unexpected query token 'value'

Hi, my entity is named "XXXValue": this has several attributes, one of these is "value". In query tab, if I do "select value from XXXValue", I get the error query token 'value'>. I try  "select XXXValue.value from XXXValue" and the error is the same. Queries on others attributes work
Forum
15

Querys slower when execute a query after every persist

The test case of the java file attachment persists many entities and executes a query ... requires only 20 sec, but the test requires 100 sec. Why the querys will be more and more slower? In ... . If you have more objects in the current transaction it takes more time (i.e. every query execution
Forum
15

Cache configuration of database file pages, query programs, query results

Are there some possibilities to configure following caches in order to keep cache data for only some important entity types and for the entire life cycle of the EntityManagerFactory. Cache of database file pages. Cache of query programs. Cache of query execution results. These caches are fully
JPA Doc
15

javax.persistence.criteria.AbstractQuery

The AbstractQuery interface defines 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
Forum
15

Query problem after transaction commit

to it. The client program can connect to the server and query to get all the records. However, after transaction ... > Test_Connection: connected 03> UI: start query [query for all object Goods successfully] 04> SELECT u FROM Goods u where u._code like :code AND u._desc like :desc  05> code= %, desc= % 06> UI: end query
Issue
15

queries under 2.7.6_4 significantly slower than under 2.7.6

indicating deep query plan checks and an overall significant performance loss in all queries ... that could possibly effect query execution. Could you please explain or post some of these logs that show deep query plan checks (and are new in 2.7.6_04)? In addition, if you can identify the exact build in
Issue
14

queries more than 10 times slower using 2.8.1 versus 2.7.6

not do any statistics generate, just tried to use the new version - our reference query that takes ... whether updating the statistics, as explained on issue #2417 post#15 helps. It seems that running your query ... more performance lose with this query, there is a good chance that the same applies to your newer
Forum
14

IN expression in a Criteria Query

, it is written that ObjectDB is 100% compatible with JPA. However, I have problem with this JPQL query ... .employeeEntity = e) ORDER BY e.name with Hibernate, there was no problem with this query, but ObjectDB throws exception: com.objectdb.o.UserException: Unexpected query token 'EXISTS' Second problem
Manual
14

Shared (L2) Entity Cache

. Cache of query programs. Cache of query execution results. The scope of these server side caches ... can also be overridden for a specific retrieval operation: // Before executing a query:   query.setHint