Internal Website Search

91-100 of 183 resultsRefresh

Criteria Query results in a NoResultException instead of returning object

a query that is equivalent to the following JPQL query: SELECT $1 ... Support identityNameProp.getName() does return "name."  Also, the JPQL ... is that the CriteriaQuery version does not return anything while the JPQL version returns the object.

How to use regular expressions in Criteria Builder

(you can use LIKE, which is less powerful). ObjectDB jpql/string#java_string_methods ... , but that extension is limited to string-based JPQL queries, as the criterial API is not extendible. support ... -based JPQL ("e.g. e.field.matches(regexp)") instead of criteria queries. support Support

First query takes 4+ minutes to complete

a transaction. 2. The 2nd EntityManager runs the queries (JPQL SELECT statements) shown ... far as I know indices are only good for fields that appear in the WHERE part of the SQL/JPQL. In ... the WHERE part of the SQL/JPQL. In our case the fields are in the ORDER part. So, I do not think an index

How to use JOIN FETCH?

The ObjectDB manual (jpql/from"> gives an example of using JOIN FETCH to avoid excessive round trips ... and you can remove duplication by using jpql/select#select

Explorer query functionality

Is there a way in the Explorer to associate JPQL queries with query result windows ... . Alternatively are you aware of any other JPA + JPQL workbench tools, commercial or ... > We don't know about other general JPA/JPQL tools that are better than the ObjectDB Explorer

Problem with distinct select, order by and equivalent alias/attribute path

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

[ObjectDB 2.5.5_03] Unexpected exception (Error 990)

am not sure if this should be the case with queries (in JPQL or SQL) because expressions are reordered ... . The NULL handling of JPQL or SQL queries is well defined. Have a look at the Persistence ... .receiveTime < :last See also jpql/path#navigation

Issue with DISTINCT Select

from criteriaquery is NOT valid JPQL) -> you get the same issue.   JPQL ... UPPER($1.profile.lastName) (which I think is not valid in JPQL but works with ObjectDB

Strange Error with Criteria API and Sorting

is justified. As explained in the jpql/order">manual ... BY clause". This is not just an ObjectDB limitation but a known JPQL and also SQL limitation

JDBC Driver for ObjectDB

queries with JPQL syntax (not SQL, except SQL queries that are also valid in JPQL). This may open