hi bruno,
this looks like a p6spy problem !
with p6spy i get the wrong result:
11 11 11 called 11 11 11
11 11 11 called 11 11 11
without p6spy the result is ok:
11 11 11 called 66 66 66
11 11 11 called 166 166 166
can you confirm this ?
jakob
Jakob Braeuchi schrieb:
hi bruno,
i made a litt
hi bruno,
i made a little testcase with a phonenumber having 1:n calls:
reportQuery = QueryFactory.newReportQuery(PhoneNumber.class, crit);
reportQuery.setAttributes(new String[]{"number","calls.numberCalled"});
iter = broker.getReportQueryIteratorByQuery(reportQuery);
while (iter.hasNext())
{
hi bruno,
could you please provide the generated sql ?
jakob
Bruno CROS schrieb:
Hi all,
It seems there is big problem on ReportQuery.
Consider 2 classes, Class_A with property_a and Class_B with property_b.
Consider that Class_A is 1:n related to Class_B.
Build a ReportQuery on Class_B
Hi all,
It seems there is big problem on ReportQuery.
Consider 2 classes, Class_A with property_a and Class_B with property_b.
Consider that Class_A is 1:n related to Class_B.
Build a ReportQuery on Class_B, requesting "property_b" and "
classA.property_a". If database field names are the sa
Le 12 sept. 05 à 17:37, Bertrand Delacretaz a écrit :
...I'm using a GROUP BY HAVING query (using addGroupBy and
setHavingCriteria to a QueryByCriteria), and depending on the data
I get an "inner hasNext was false" error.
IIUC the problem is due to the SELECT COUNT [2] query used by OJB
t
