About named queries

forum_thread

Join query problem with new statetment

Hi, I'm trying to implement some reporting logic in my application and got nasty exception when using query with join. The query code is: #1 2011-07-04 19:40 Hi, I'm trying to implement some reporting logic in my application and got nasty exception when using ...

 
release

2.4.5

... on using a no arg function in criteria queries ( issue #174 ). Fixed activation when there is no MAC ... Fixed a regression bug in using primary key fields in queries. Fixed a regression bug of duplicating new objects on ... . Fixed exception when a named query doesn't exist to IllegalArgumentException . ...

 
forum_thread

Problem with byte arrays in JDO - internal exception

This code generates an internal exception: ... There was a bug in handling JDO delete queries. Please try build 2.7.1_07. ObjectDB ...

 
issue

Issues with JDO Casting & Full Qualified Names

hi! See this query and the comments about failures. This is really urgent for us because as you've stated, this is the only workaround for now to proper casting AND map KEY access though it isn't working correctly either.. Bug Version: Priority: Normal Status: Closed Replies: 1 Type:  Bug ...

 
forum_thread

Problem with byte arrays in JDO - ClassCastException

A bizarre ClassCastException is thrown if I attempt to obtain a byte array field as the result of a Query: Exception in thread "main" java.lang.ClassCastException: java.lang.Boolean cannot be cast to [B at spiffy.test.ObjectdbTest.main(ObjectdbTest.java:44) #1 2017-09-13 03:33 A bizarre ClassCastException is thrown if I attempt to obtain a byte array field as the result of a Query: ...

 
forum_thread

Querys slower when execute a query after every persist

The test case of the java file attachment persists many entities and executes a query after every persist. The execution time amounts 2 sec when the test persists 1000 entities. The execution time amounts 100 sec when the test persists 10000 entities. We have been expected that the second case requires only 20 sec, but the test requires 100 sec. Why the querys will be more and more slower? In addition there are a cpu snapshot for visual vm and an image of cpu snapshot as attachment. #1 2015-09-18 10:43 The test case of the java file attachment persists many entities and executes a query after every persist. ...

 
release

2.4.2

... composite indexes . Improved processing of queries with a large number of variables ( issue #114 ). Improved toString of criteria queries to use aliases ( issue #12 7). Changed non loaded ... . Fixed exception when a named query doesn't exist to IllegalArgumentException . ...

 
forum_thread

Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x

Hi, I upgraded the odb file using converter.jar which is having 15943 entry. Previously, with object 1.x, the same query was getting executed within an seconds and now the same is taking around 40 seconds in object db 2.x I have build the query using the follwoing Query query = persistanceManager.newQuery("LogEntryAttrebuteImpl.calss", "typeIndexes.contains(this.type) && logEntryIdList.contains(this.logEntryId)"); #1 2012-09-07 15:06 Hi, I upgraded the odb file using converter.jar which is having 15943 entry. Previously, with object 1.x, ...

 
release

2.4.1

... composite indexes . Improved processing of queries with a large number of variables ( issue #114 ). Improved toString of criteria queries to use aliases ( issue #12 7). Changed non loaded ... . Fixed exception when a named query doesn't exist to IllegalArgumentException . ...

 
release

2.4.3

... composite indexes . Improved processing of queries with a large number of variables ( issue #114 ). Improved toString of criteria queries to use aliases ( issue #12 7). Changed non loaded ... . Fixed exception when a named query doesn't exist to IllegalArgumentException . ...