9 | Problem with distinct select, order by and equivalent alias/attribute path from your point of view? Thanks and regards Benjamin Klink bklink Benjamin Klink JPQL restricts ... to generate valid JPQL queries. support Support 1. Even if maybe obsolete because of point 2. I'm |
9 | New to Product & Having An Issue with the use of @Embedded, @EmbeddedId or with my JPQL queries or is this a bug? Any help ... , generating new departmentId. I am looking now at the JPQL query issues, which might indicate |
9 | multiple different applications access one odb file JPQL syntax only (not SQL, except SQL queries that are also valid in JPQL), and then iterating |
9 | ClassCastException on SELECT NEW ... after UPDATE over Java RMIHi, 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 |
9 | How to use regular expressions in Criteria Builder an extension, but that extension is limited to string-based JPQL queries, as the criterial API is not ... in queries, just use string-based JPQL ("e.g. e.field.matches(regexp)") instead of criteria queries. support Support |
9 | Help with 'not like/lower' query William You are talking about criteria queries but your first query is a JPQL query. Is it the JPQL |
9 | 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 ... are not supported in either string based JPQL or criteria queries. support Support |
1 | JDBC Driver for ObjectDB, for SELECT queries with JPQL syntax (not SQL, except SQL queries that are also valid in JPQL |
1 | [ObjectDB 2.5.5_03] Unexpected exception (Error 990) with queries (in JPQL or SQL) because expressions are reordered as part of the query optimization. support Support I did some research on this topic. The NULL handling of JPQL or SQL queries is well defined |
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 1254 (JPA JPQL WHERE clause for IN :variable not working if variable |
