About jpql

81-90 of 139Refresh
Forum
2

First query takes 4+ minutes to complete

the queries (JPQL SELECT statements) shown next.  Query We test with the following query: SELECT r from ... in the WHERE part of the SQL/JPQL. In our case the fields are in the ORDER part. So, I do not think ... that appear in the WHERE part of the SQL/JPQL. In our case the fields are in the ORDER part. So, I
Issue
2

Issue with DISTINCT Select

because the generated code from criteriaquery is NOT valid JPQL) -> you get the same issue.   thanks ... ? this is really confusing, I so much often wish to have a better interface than JPQL :( Thanks, Alex Why not ... .lastName) (which I think is not valid in JPQL but works with ObjectDB). You can also use: SELECT
Issue
1

@Enumerated(EnumType.STRING) annotation inhibits proper execution of IN expressions.

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 681 (JPA JPQL WHERE clause for IN :variable not working if variable is a list
Issue
1

[ObjectDB 2.5.5_03] Unexpected exception (Error 990)

if this should be the case with queries (in JPQL or SQL) because expressions are reordered as part of the query optimization. I did some research on this topic. The NULL handling of JPQL or SQL queries
Forum
1

ClassCastException on SELECT NEW ... after UPDATE over Java RMI

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
Forum
1

Help with 'not like/lower' query

on this.   Thanks You are talking about criteria queries but your first query is a JPQL query. Is it the JPQL
Forum
1

JPA 2.0 Criteria API: (When) Fully supported ?

implementation creates a JPQL query string for fetching while the JPA 2.0 implementation uses Criteria API ... ), so these elements are not supported in either string based JPQL or criteria queries. verlsnake
Forum
1

JPA does not seem to be db agnostic

)); return em.createQuery(query).getSingleResult(); } 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. kasavbere
Issue
1

JPA Query Criteria API (JPA 2.0)

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.   Implementation of the JPA Criteria Query API was just added
Forum
1

native sql queries

queries are not supported because there is no underlying RDBMS. But since SQL and JPQL are very similar it could be possible in future releases to support "native SQL". But JPQL is preferred