About GROUP BY

forum_thread

Out of memory

Hi, Today in the middle of the night ODB just crashed leaving this on console screen: ... large. The strange thing is - allocated memory by storage threads stops at the size of database. Maybe there is some kind of ... that return a lot of data, as well as queries that use GROUP BY and ORDER BY, in which large data has to be processed. Unfortunately ...

 
forum_thread

Exception when dataset bigger than treshold

I was working on reporting service for my application and found a problem with datasets bigger than treshold set in objectdb.conf.   ... java.lang.Thread.run(Thread.java:636) [na:1.6.0_24] Caused by: java.io.FileNotFoundException: /tmp/ObjectDB/789641482/BatchQueryItr_0.fls ... ODB server is running as odb user and odb group. Doctor on the same database, which is quite big: -rw-r--r-- 1 ...

 
issue

Unexpected error when loading all entity instance

Hi, when going through all entity instance to find orphaned entries we get the exception: ... exception ( Error 990 ) Generated by Java HotSpot ( TM ) 64 - Bit Server VM 1.8.0_74 ( ... Sections with Errors -------------------------- Group #1: Page #326 141:'01f1e2e0-12cb-11e7-bda5-f6e38e607e99' 1/2 ...

 
forum_thread

Query vs Extent for retrieving data

I'm running into a problem where data that is retrieved via a Query comes out null, but when I retrieve it using an Extent everything is present. We have a very simple class: public class PositionReportManagerBean implements InstanceCallbacks { private int maxReports; private List<PositionReportBean> reports; } I have a test file with 5 instances of PositionReportManagerBean, each with maxReports set to 10 and 5 PositionReportBeans in reports. I can verify with the ObjectDB explorer that all of the data is there. If I call ... I need to set on the Query? I'm really stumped by this one. edit ... Avoid overflow of published source code examples by breaking long lines . You may mark in paragraph code words ...

 
forum_thread

Problem on JPA Merge Entity.

Hello, I have a problem with the EntityManager.merge() function. I set a property value of an entity (statement) with an other entity (newSingleConstraint). newSingleValue is already persisted. I do this myself (no use of cascade because sometimes the newSingleValue is already in database).   The statement update don't throw exception. And when i try to reload statement the value i have set before is a null value. I check with the Explorer, the statement has a null value on the property and the newSingleValue is present.... i update. The statement's property is typed by a class that is a superclass of the newSingleValue. This the chain ... Avoid overflow of published source code examples by breaking long lines . You may mark in paragraph code words ...