About results

release

2.6.5

... in handling large objects with long primary keys as query results ( issue #260 ). Fixed detachment of embedded objects to ... Fixed a bug of returning managed hollow objects in query results. Fixed an error message for invalid DELETE query ( issue ...

 
forum_thread

JPA and handling large data sets

This is not a rellay ObjectDB problem, rather a JPA problem. Our web-based DB supports Hibernate or JPA (ElicpseLink/ObjectDB). We implemented a export/import class to export the whole database or single datasets (domains) in a persistence layer/database independent format. This class works fine - DB exports form a Hibernate/MySQL base via the independent formt to ObjectDB is possible. But exporting large binary data sets is very slow. To avoid memory problems the binary data type is read step by step during the export with the  query/setFirstResult() & setMaxResults().... order value. For example, if your query returns results ordered by the primary key, use the value of the primary key of the ...

 
manual

Database Management Settings

Explains settings and performance tuning of the ObjectDB Java object database for JPA/JDO.... priority = "40" /> <query-cache results = "32mb" programs = "500" /> <extensions ... <query-cache> element <query-cache results = "32mb" programs = "500" /> The ...

 
issue

Strange Error with Criteria API and Sorting

We're creating a simple selection (distinct) including an order clause. When watching the created criteria in debugger we get the correct expression: SELECT DISTINCT $1 FROM MyEntity $1 WHERE ((TYPE($1)=class test.MyEntity)) ORDER BY UPPER($1.name) DESC You can see that in the order by there's correctly a "$1" var. Running this (without the type thing before) in the explorer correctly returns the sorted results. However, running this with the criteria API produces this error: ... thing before) in the explorer correctly returns the sorted results. However, running this with the criteria API produces this ... Invalid order expression '$2' for distinct results at com.objectdb.o.MSG.d(MSG.java:61) [objectdb-2.4.4_05.jar:] at ...

 
forum_thread

Possible issue with timestamps

Hi, If I query doing something like: select c from CDI c where c.creationDate > {ts '2012-03-29 11:00:00} and c.creationDate < {ts '2012-03-29 12:00:00'} the test fails. Its ONLY for 12:00:00. When I started digging I found that if I queried 00:00:00 to 00:25:00 and then did 12:00:00 to 12:25:00 I got IDENTICAL results. For some reason 12:00:00 is being treated the same as 00:00:00. All other hours seem to be fine. ... 00:25:00 and then did 12:00:00 to 12:25:00 I got IDENTICAL results. For some reason 12:00:00 is being treated the same as 00:00:00. All ... , CDI. class ) ; List<CDI> results = query2. getResultList ( ) ; ...

 
forum_thread

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

I have a simple task to validate the sample code will switch over to the slave database when the master is unavailable. I simulate the master unavailable by stopping the master server; which generates the following exception below. What am I doing wrong? It appears the connection manager fails to try the second URL in the list: objectdb://10.9.2.15:9998//10.9.2.15:9999/test.odb;user=admin;password=password Thank you in advance. ... = "10" / > <query - cache results = "32mb" programs = "500" / > ... = "10" / > <query - cache results = "32mb" programs = "500" / > ...

 
issue

Large query parameter - out of memory

I have an entity object composed of an id, large data in the form of a string and the hashcode of the string as an index. The attached test saves 2000 of these objects, writing the data to a txt file as it goes. It then loops through the data from the file and queries for the entity id based on the data hashcode and the data itself. Bug Version: Priority: Normal Status: Fixed Replies: 1 Type:  Bug ...

 
api-jpa

javax.persistence.NonUniqueResultException

Thrown by the persistence provider when Query.getSingleResult() or TypedQuery.getSingleResult() is executed on a query and there is more than one result from the query.(Exception of JPA)

 
release

2.6.2

... Fixed a bug of returning managed hollow objects in query results. Fixed an error message for invalid DELETE query ( issue ... in using JPQL operations (e.g. UPPER ) in DISTINCT results. Fixed an exception in handling user defined serializable ...

 
api-jpa

javax.persistence.NoResultException

Thrown by the persistence provider when Query.getSingleResult() or TypedQuery.getSingleResult()is executed on a query and there is no result to return.(Exception of JPA)