About result

forum_thread

Queries are slow on a large database

Hi, I have a 12GB database with 787603 entries. It is much larger than usual and there are performances issues. I am doing small queries and they take much longer than I expect, i.e.: Get the total number of entries Get 25 consecutive entries (i.e. 0-25) Get one specific entry On average each query needs 4 to 5 minutes to return a result. I have been adviced to use indexes but they are already used through the JDO Metadata file. For instance I use this class: ... On average each query needs 4 to 5 minutes to return a result. I have been adviced to use indexes but they are already used ...

 
forum_thread

java.sql.Date equals comparison not working with CriteriaAPI

Hello, Using ODB 2.4.5 and the Criteria API, doing a simple equals comparison with java.sql.Date value doesn't match any results in the database. Our code looks like this: ... ) ; System. out . println ( "Result Size: " + resultList. size ( ) ) ; ... SELECT $1 FROM MyDateEntity $1 WHERE $1.date=:$$cmlp1 Result Size: 1 The Predicate's toString is irrelevant. As can ...

 
release

2.7.2

... in queries. Fixed a bug in ordering query result by an expression that is used in IN operator. Fixed a ... ( issue #249 ). Improved title of query result windows in the Explorer. Changed the Enhancer to return ...

 
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. #1 2012-03-29 05:07 Hi, If I query doing something like: select c from CDI c where c.creationDate > {ts '2012-03-29 11 ...

 
manual

Database Management Settings

Explains settings and performance tuning of the ObjectDB Java object database for JPA/JDO.... The results attribute specifies the size of the query result cache. Caching results is very useful for recurring queries with ...

 
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. #1 2013-05-06 20:16 I have a simple task to validate the sample code will switch over to the slave database when the master is unavai ...

 
forum_thread

Fantom

  Hi, so far I've been able to get ObjectDb to persist objects from many JVM languages, eg.: Java/Groovy/Scala/Kotlin. However, I can't seem to get Fantom to work. Anyone tried this yet? Dave     ... { Str ? street } Result Groovy version works fine, using the ObjectDb ObjectExplorer ...

 
release

2.6.5

... ( issue #249 ). Improved title of query result windows in the Explorer. Changed the Enhancer to return ... non public persistable types. Fixed the result type of a sum query on a single value. Version 2.5.6 ...

 
forum_thread

First query takes 4+ minutes to complete

Hi, we are evaluating ObjectDB 2.5.1_04 in embedded mode hoping to replace SQLite in our application. We observed that in our case it takes on average more than 4 minutes to complete the first SELECT query that we run on the DB which contains about 320,000 records of a single type of object. SQLite in comparison responds within few seconds on average with the same number of records. We hope to receive your recommendation on how to improve this result with this post.   Test System ... hope to receive your recommendation on how to improve this result with this post.   Test System We are ... , r . channelNumber DESC We limit the result to 50 records. Basically we wish to get the last 50 records ...

 
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: ... ( true ) ; List<TestEntity> result = em. createQuery ( query ) . getResultList ( ... ) ;   for ( TestEntity e : result ) { System. out . println ( "Name: " ...