ObjectDB Database Search

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

;NullPointerException in com.objectdb.o.ENH.b() when resolving entity names in JPQL ... .hydraorm.domain.entities.workforce.Driver) instead of entity names ("Driver") in JPQL queries to bypass

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

string ( JPQL ) by toString() on the criteria query. support Support

I tested ObjectDB. When I write JPQL , I get this error. Caused by: com.objectdb.o.InternalException: Error reading UTF string at com.objectdb.o.BYR.U(BYR.java:1217) at com.objectdb.o.BYR.U(BYR.java:523) at com.objectdb.o.BYR.L(BYR.java:504) at com.objectdb.o.QJD.a(QJD.java:241) at com.objectdb.o

queries (as an extension to JPQL and JDOQL) you can use the Normalizer expression directly in the query

.get('location') = 'California' This is not a valid JPQL query but an extension that ObjectDB

I am afraid it is not supported neither in JPQL nor in criteria queries. But does it make sense

ObjectDB 2.3 has been released and it includes important additions and fixes: Added the ability to edit databases in the Explorer ( issue #2 ). Added the ability to execute queries in the Explorer (issue #3 ). Other small Explorer improvements. Added support of IN operator in JPQL queries. Added

"(" and the "LIMIT". Is it possible de make a sub request in a JPQL query ? dwighthaul Paul

of eager fetch in JPQL as follows: SELECT c FROM C JOIN FETCH c.bList WHERE c.id=:id But when I attempt

I've got this class... @Entity @Table(name = "language") public class Language implements Serializable{ ... private List aliases; ... public boolean hasAlias(List alai) { return ... ; } ... } When I try to make this JPQL query: SELECT g from Language g where g.hasAlias("espanol", "italian

expressions, which are not allowed in JPQL Update queries. See discussions on this issue . ObjectDB

Greetings, I was playing aroung with JPQL and have found that there is a problem with "is null" queries. When you use "is null" in where clause, query runs correctly, but results are incorrect. Let me show you an example: - entity @Entity public class EntityA {     @Id  

objectdb only permit direct SQL coding? cpanon CP ObjectDB doesn't support SQL but JDOQL and JPQL

Greetings ObjectDB team, All below questions assume a very large database (~1,000,000,000 objects): Q1: In what cases would ObjectDB utilize multi-threading ? how about in JOIN operations ? Q2: Is it true that two read-only JPQL queries accessing the same database file actually run 

string) query for example: SELECT FROM MyEntity WHERE this.enumSet.contains(:arg) JPA/ JPQL  

well perhaps my choice of topic is what's incorrect. explorer executes a user's JPQL query and it certainly

The ObjectDB manual ( https://www.objectdb.com/java/jpa/query/ jpql /from ) gives an example of using JOIN FETCH to avoid excessive round trips to the database: SELECT c FROM Country c JOIN FETCH c.capital I've tried a few variants of the following example, and haven't been able to get this to work

We are using ObjectDB 2.5.1_04. The following JPQL query causes an internal exception: SELECT COUNT(r) FROM RecordingMetaData AS r WHERE ((r.mapFromCli LIKE '192.168.10.13%' ESCAPE '\')) The exception: Caused by: java.lang.IllegalStateException: com.objectdb.o.InternalException: Unexpected

Hello, I am learning ObjectDB and i noticed that the queries that are executed in  ObjectDB Explorer are faster (about 5 ms) than queries in my project (~400 ms). Here is my JPQL query :  SELECT p FROM Point p WHERE p.x=0 I am using Point entity class from tutorial

standard JPQL and it would be less efficient since indexes cannot be used. support Support Thanks

of JPQL / EJB QL is available for both Birt (using an external extension) and Jasper

that you can use: SELECT FROM Inspiration IMPORT homplex.model.dbobject.* and ObjectDB supports it also in JPQL

; } Is there a more optimal way to do this? DragonRulerX Jared Hinze You can use JPQL Locate : SELECT FROM Program

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

(inverse) relationships. Fixed a bug in using IN expression in criteria queries . Fixed processing an IN(:param) expression in JPQL queries.

loader issue when using GWT/Jetty. Fixed a bug in using fields of embedded primary key in JPQL queries.

Added support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer About dialog boxes. Fixed an UPDATE/DELETE query bug in client-server mode. Fixed an ArrayIndexOutOfBoundsException in retrieval of large objects. Fixed Explorer display

Added the ability to edit databases in the Explorer ( issue #2 ). Added the ability to execute queries in the Explorer (issue #3 ). Other small Explorer improvements. Added support of IN operator in JPQL queries. Added support of ";drop" database url parameter. Adjusted the Enhancer to the new

Added support for a JPQL update query with multiple variables (issues #2369, #3009)

, which are not allowed in JPQL Update queries. See discussions on this issue . ObjectDB should produce

The ObjectDB BIRT/ODA driver is an extension of the open source Business Intelligence and Reporting Tools (BIRT) that adds support of ObjectDB as a data source and JPQL as a data set query language. In the current implementation ObjectDB is embedded in the driver. Any 2.x version of the driver

This UPDATE query is invalid because JPQL UPDATE queries are limited to setting values not