ObjectDB Database Search

gzdillon Lai Yang The length field of arrays is not supported by JDOQL / JPQL queries. You may maintain

I am trying to run ObjectDB first time in a production server. Operating System: Ubuntu Ubuntu 22.04.1 LTS ObjectDB Version: 2.8.8 (Downloaded) ObjectDB version in Maven: 2.8.8 (I don't know how comes 2.8.1 comes in the error message) When I try to run jpql , it gives this error [ObjectDB 2.8

Possible issue for JPQL IN expression with a set of more than one string literals values in the path expression. Error: Exception in thread "main" [ObjectDB 2.3.7_10] SELECT e FROM MyEntity e WHERE e.country IN ('US' == ,

Possible issue for JPQL IS EMPTY comparison expression: SELECT e FROM MyEntity e WHERE e.collection-valued IS EMPTY throws javax.persistence.PersistenceException: Invalid operand type  for operator IS EMPTY (error 756) Thanks. Note: It doesn' t work with SIZE(): SELECT e FROM MyEntity e

JPQL features are not supported yet by ObjectDB. The main missing feature is subqueries

Hi, I know a single command in MySQL can find repeated records: Select * from TTT t where id in (select id from TTT s group id having count(id)1) I dont know how to do this using JPQL , but I use query from 430,000 records and put them into hashmap, finally it cost one hour and failed: Exception in

JPQL UPDATE queries. A better error message should be produced by ObjectDB. See also this forum thread .   support Support

JPQL query to get entities that does not have a child entity in their child entities

KEY() / VALUE() not recognized in JPQL??

CASE WHEN...THEN...ELSE...END not working using JPQL/JDOQL

JPQL 2.0 adds support of CASE statements for conditional expressions in queries, similarly to switch/case/default in Java, and based on the SQL syntax. Case statements are currently not supported by ObjectDB. support Support I wish to express also my interest in CASE statement support, which I

JPQL support for mapped by (inverse) collections

is invalid. You cannot navigate through collections in JPQL directly. You have to use JOIN to define ... to the standard JPQL . The following 2 queries are now equivalent: select count(f) from Foo f where f ... is a bit longer but it is JPA portable. ObjectDB can enforce using standard JPQL by setting

. Since: Jakarta Persistence (JPA) 2.0 The Paths and Types in JPQL and Criteria API article explains

. Since: Jakarta Persistence (JPA) 2.0 The Logical Operators in JPQL and Criteria API article explains

Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.Order An object that defines an ordering over the query results. Since: Jakarta Persistence (JPA) 2.0 The ORDER BY clause ( JPQL / Criteria API) article explains how to use Order . Public Instance Methods Expression getExpression

Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.Selection Type Parameters: - the type of the selection item Super Interfaces: TupleElement The Selection interface defines an item that is to be returned in a query result. Since: Jakarta Persistence (JPA) 2.0 The SELECT clause ( JPQL

Persistence (JPA) 2.0 The FROM clause ( JPQL / Criteria API) article explains how to use Root

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

Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.Expression Type Parameters: - the type of the expression Super Interfaces: Selection , TupleElement Type for query expressions. Since: Jakarta Persistence (JPA) 2.0 The JPA Query Expressions ( JPQL / Criteria) article explains

Persistence (JPA) 2.0 The FROM clause ( JPQL / Criteria API) article explains how to use Join . Public

Jakarta Persistence (JPA) Interface jakarta.persistence.Query Interface used to control query execution. See Also: TypedQuery StoredProcedureQuery Parameter Since: Jakarta Persistence (JPA) 1.0 Chapter 4 - JPA Queries ( JPQL / Criteria) explains how to use Query . Public Instance Methods int

Jakarta Persistence (JPA) Interface jakarta.persistence.Parameter Type Parameters: - the type of the parameter Type for query parameter objects. See Also: Query TypedQuery Since: Jakarta Persistence (JPA) 2.0 Chapter 4 - JPA Queries ( JPQL / Criteria) explains how to use Parameter . Public Instance

implements Serializable { // ... } I have a JPQL query that looks like this: String jpql = "Select vtm ... "); System.out.println(" JPQL : " + temSQL); System.out.println("Parameters: " + parameters); TypedQuery ... navigateToListAllVtms() { System.out.println("navigateToListAllVtms"); String jpql = "Select vtm " + " from Vtm vtm

to do ad-hoc JPQL queries and navigate through the results and even make small changes to primitive ... that are valid in queries ( JPQL , JDOQL and ObjectDB extensions)  are supported.  SHA1.hash ... about using a Java expression to set a value when editing a field, not a JPQL expression in a query

().equals("")) { return cs; } String jpql ; Map m; m = new HashMap(); jpql = "select new lk.gov ... = " + m); System.out.println("j = " + jpql ); cs = (List ) getFacade().findLightsByJpql( jpql , m ... Method in Abstract Facade public List findLightsByJpql(String jpql , Map parameters) { Query qry

, it is written that ObjectDB is 100% compatible with JPA. However, I have problem with this JPQL query ... . The problem I was getting, was a syntax error when the "IN (:bindVar)" was used within a JPQL query ... The original post was on criteria queries, but it is the same with JPQL , since criteria queries

to the corresponding function in JPQL . Parameters: x - expression for string to be searched pattern - string

: the order of the parameters of this method is reversed compared to the corresponding function in JPQL

: the order of the parameters of this method is reversed compared to the corresponding function in JPQL

compared to the corresponding function in JPQL . Parameters: x - expression for string to be searched

to the following JPQL query: SELECT $1 FROM IdentityObject $1 WHERE $1.name='demo' You have to use ... that can be run?   support Support identityNameProp.getName() does return "name."  Also, the JPQL ... ; My issue is that the CriteriaQuery version does not return anything while the JPQL version returns

updates. But, when using the JPQL Query, the list are refreshed, and, when I querying ... CriteriaBuilder to JPQL or from Entity to Primitive. What´s now? flavioreboucassantos Flávio Rebouças ... criteria queries and string based JPQL queries regarding the cache (and actually every criteria

select count(e.id) from Page e 1 java.lang.Long: 161143 Time : 23.889999 JPQL select count(e.sUrl) from Page e 1 java.lang.Long: 161143 Time : 96.968002 JPQL select count(e.iSize) from Page e 1 java.lang.Long: 161143 Time : 10.359000 JPQL The command tool is from the book of Mike Keith. Obviously

EntityManager runs the queries ( JPQL SELECT statements) shown next.  Query We test ... / JPQL . In our case the fields are in the ORDER part. So, I do not think an index will help ... the WHERE part of the SQL/ JPQL . In our case the fields are in the ORDER part. So, I do not think an index

Is there a way in the Explorer to associate JPQL queries with query result windows?  I ... are you aware of any other JPA + JPQL workbench tools, commercial or otherwise that would support this? paul ... and view several query result windows. We don't know about other general JPA/ JPQL tools

and regards Benjamin Klink bklink Benjamin Klink JPQL restricts ORDER BY expressions to expressions ... these queries? It would probably be better to repair that library to generate valid JPQL queries

for ObjectDB, if it helps.  It will support running SELECT queries in JPQL syntax only (not SQL, except SQL queries that are also valid in JPQL ), and then iterating over a result sets, as in ordinary

Hi, we are using ObjectDB 2.5.4_04 on Linux. Our application, which uses ObjectDb as a DB, exposes a Java RMI interface which allows remote RMI clients to run JPQL queries on the DB. The application ... NEW ...) and UPDATE JPQL queries on the DB via the RMI interface. What we noticed

expressions in queries as an extension, but that extension is limited to string-based JPQL queries, as ... so you can use regular expressions in queries, just use string-based JPQL ("e.g. e.field.matches(regexp)") instead of criteria queries. support Support

; JOIN close is invalid in JPQL . Instead of ON you may  include all the variables in ... JOIN of JPQL . support Support Hi, this is my critera query: CriteriaBuilder cb = entityManager

William You are talking about criteria queries but your first query is a JPQL query. Is it the JPQL

implementation creates a JPQL query string for fetching while the JPA 2.0 implementation uses Criteria ... statements ( issue #14 ), so these elements are not supported in either string based JPQL or criteria queries. support Support

A valid JPQL query must include SELECT, otherwise the query is incomplete. Some JPA implementations extend the standard JPQL by supporting queries with no SELECT. support Support

Hi, Is it possible to get a JPQL string having a Query object instance? JpaQuery class doesn't have any method like "getQueryString" or "getDatabaseQuery", maybe it's going to be added in near ... with JPQL string and parameters map to find and optimize the most ineffective cases. kborkowski

.labels Is it a bug or JPQL query is wrong? Best regards, Pablo. Pablo Berra Pablo Berra This seems to be the result of how JPQL queries are converted into SQL like syntax before executing. MEMBER ... Thank you for your answer. So, if it is a JPQL parsing/conversion problem, can I avoid that using

more issues in explorer because the generated code from criteriaquery is NOT valid JPQL ) - you get the same ... than JPQL :( Thanks, Alex quasado Alexander Adam Why not: SELECT DISTINCT $1 FROM IndividualContact $1 LEFT JOIN $1.profile $2 ORDER BY UPPER($1.profile.lastName) (which I think is not valid in JPQL but works

driver, for SELECT queries with JPQL  syntax (not SQL, except SQL queries that are also valid in JPQL ). This may open ObjectDB for read-only applications, such as reporting. support Support

When the following annotation is present on an enum type entity field: @Enumerated(EnumType.STRING) Queries using JPQL IN expressions on this field won't work correctly anymore. This issue has been described in forum post 1254  (JPA JPQL WHERE clause for IN :variable not working if variable

The JPA Criteria API supports dynamic definition of JPQL queries using CriteriaBuilder as a factory. ObjectDB supports dynamic definition of JPQL queries as strings. Support of the new JPA 2 Criteria API in expected in future versions. support Support   Implementation of the JPA Criteria