Internal Website Search

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

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

to mariadb or mysql using native java JPA API and in some cases JPQL or must i store to an Objectdb unique

may be valid in Hibernate HQL but not in JPQL and JPA Criteria API. support Support My apologies, in

Copied a straightforward entity class from my coleague. Using Eclipse Kepler (Reporting) and stored it in ObjectDB 2.5.3_02. After creating an ObjectDB BIRT DataSource and a DataSet, entered a simple JPQL query to select the fields. Entity looks like this: package entity; import java.util.Date

methods in queries to provide your own spatial extension to JPQL . Obviously this is not a complete

? Is it something specific to ObjectDB? Is it a bug? This behavior appears with JPQL and with equivalent

in a query (since ObjectDB supports user defined methods in queries as an extension to JPQL

But what about: http://www.objectdb.com/java/jpa/query/ jpql /comparison Section "Comparable Data Types" Comparison

You cannot select a list, so this is an invalid JPQL query. SELECT s FROM PulseDataWareHouse w JOIN w

Hi What is the way to extract data from ObjectDB to relational databases (Oracle). We need to feed an Oracle database with data for reporting/datawarehosing. Should JPQL be used or is there some tools to do it. Thanks. peric.emil Emil Perić Currently there is no such tool

", value); What do you guys think about it?   lwalkowski Lukasz Walkowski You can use a JPQL

? thanks! Alex quasado Alexander Adam You can use a JPQL query with a simple date comparison: SELECT p

I prefer to keep custom JPQL named queries in an external file, e.g. orm.xml, rather than in the entity classes, for example: delete from DataValue d where d.capabilityId = :capabilityId and d.creationtime

id WHERE item.sku = :key OR id = :id ORDER BY item.sku DESC You may also try this (not valid JPQL

Hibernate API / extensions (e.g. Session instead of EntityManager , queries with HQL syntax instead of JPQL

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

, 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

an ad-hoc JPQL query, and then browse/edit the results. This would be incredibly useful. Thanks

issue #632  and  issue #634 ). Fixed a bug in using JPQL operations (e.g. UPPER ) in

. Since casting in not part of JPQL and rarely used I am afraid it might not be the last problem