You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Bruno CROS <br...@gmail.com> on 2006/02/17 18:01:27 UTC
ReportQuery bug 1.0.4
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 same in each table for
property_a and property_b, surprise, that you believe the value of
property_b is the property_a one !!
I looked to the generated query, and, awful, aliases are wrong.
Anyone confirms ?
OJB 1.0.4 (bug wasn't related in 1.0.1)
How many databse fields with the same name i have into my model? Too much !!
Thanks. Regards.
Re: ReportQuery bug 1.0.4
Posted by Bruno CROS <br...@gmail.com>.
Hello.
Does someone find a free alternative to P6SPY, ( or a fix to mixed
alias bug) ?
thank you
On 2/20/06, Bruno CROS <br...@gmail.com> wrote:
>
> Yes, I confirm.
>
> it's P6SPY. I have no idea why, at all.
>
> It's gonna be hard to debug queries with that kind of behaviour. I hope
> P6spy will be fixed soon.
>
> Thanks a lot.
>
>
>
>
> On 2/17/06, Jakob Braeuchi <jb...@gmx.ch> wrote:
> >
> > 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 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())
> > > {
> > > Object[] data = (Object[]) iter.next();
> > > System.out.println(data[0] + " called " + data[1]);
> > > }
> > >
> > > the sql looks quite ok:
> > > SELECT A0.NUMBER,A1.NUMBER FROM PHONE_NUMBER A0 INNER JOIN CALLS A1 ON
> > > A0.PHONE_NUMBER_ID=A1.PHONE_NUMBER_ID WHERE A1.NUMBER LIKE '%66%'
> > >
> > > but the data retrieved from the resultset is wrong:
> > >
> > > number and calls.numberCalled contain the same value :(
> > >
> > > jakob
> > >
> > >
> > >
> > > Jakob Braeuchi schrieb:
> > >> 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, requesting "property_b" and "
> > >>> classA.property_a". If database field names are the same in each
> > >>> table for
> > >>> property_a and property_b, surprise, that you believe the value of
> > >>> property_b is the property_a one !!
> > >>>
> > >>> I looked to the generated query, and, awful, aliases are wrong.
> > >>>
> > >>> Anyone confirms ?
> > >>>
> > >>> OJB 1.0.4 (bug wasn't related in 1.0.1)
> > >>>
> > >>> How many databse fields with the same name i have into my model? Too
> >
> > >>> much !!
> > >>>
> > >>> Thanks. Regards.
> > >>>
> > >>>
> > >>>
> > >>>
> > ------------------------------------------------------------------------
> > >>>
> > >>> No virus found in this incoming message.
> > >>> Checked by AVG Free Edition.
> > >>> Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date:
> > >>> 17.02.2006
> > >>>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> > >> For additional commands, e-mail: ojb-user-help@db.apache.org
> > >>
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail: ojb-user-help@db.apache.org
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: ojb-user-help@db.apache.org
> >
> >
>
Re: ReportQuery bug 1.0.4
Posted by Bruno CROS <br...@gmail.com>.
Yes, I confirm.
it's P6SPY. I have no idea why, at all.
It's gonna be hard to debug queries with that kind of behaviour. I hope
P6spy will be fixed soon.
Thanks a lot.
On 2/17/06, Jakob Braeuchi <jb...@gmx.ch> wrote:
>
> 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 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())
> > {
> > Object[] data = (Object[]) iter.next();
> > System.out.println(data[0] + " called " + data[1]);
> > }
> >
> > the sql looks quite ok:
> > SELECT A0.NUMBER,A1.NUMBER FROM PHONE_NUMBER A0 INNER JOIN CALLS A1 ON
> > A0.PHONE_NUMBER_ID=A1.PHONE_NUMBER_ID WHERE A1.NUMBER LIKE '%66%'
> >
> > but the data retrieved from the resultset is wrong:
> >
> > number and calls.numberCalled contain the same value :(
> >
> > jakob
> >
> >
> >
> > Jakob Braeuchi schrieb:
> >> 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, requesting "property_b" and "
> >>> classA.property_a". If database field names are the same in each
> >>> table for
> >>> property_a and property_b, surprise, that you believe the value of
> >>> property_b is the property_a one !!
> >>>
> >>> I looked to the generated query, and, awful, aliases are wrong.
> >>>
> >>> Anyone confirms ?
> >>>
> >>> OJB 1.0.4 (bug wasn't related in 1.0.1)
> >>>
> >>> How many databse fields with the same name i have into my model? Too
> >>> much !!
> >>>
> >>> Thanks. Regards.
> >>>
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------
> >>>
> >>> No virus found in this incoming message.
> >>> Checked by AVG Free Edition.
> >>> Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date:
> >>> 17.02.2006
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> >> For additional commands, e-mail: ojb-user-help@db.apache.org
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: ojb-user-help@db.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>
Re: ReportQuery bug 1.0.4
Posted by Jakob Braeuchi <jb...@gmx.ch>.
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 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())
> {
> Object[] data = (Object[]) iter.next();
> System.out.println(data[0] + " called " + data[1]);
> }
>
> the sql looks quite ok:
> SELECT A0.NUMBER,A1.NUMBER FROM PHONE_NUMBER A0 INNER JOIN CALLS A1 ON
> A0.PHONE_NUMBER_ID=A1.PHONE_NUMBER_ID WHERE A1.NUMBER LIKE '%66%'
>
> but the data retrieved from the resultset is wrong:
>
> number and calls.numberCalled contain the same value :(
>
> jakob
>
>
>
> Jakob Braeuchi schrieb:
>> 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, requesting "property_b" and "
>>> classA.property_a". If database field names are the same in each
>>> table for
>>> property_a and property_b, surprise, that you believe the value of
>>> property_b is the property_a one !!
>>>
>>> I looked to the generated query, and, awful, aliases are wrong.
>>>
>>> Anyone confirms ?
>>>
>>> OJB 1.0.4 (bug wasn't related in 1.0.1)
>>>
>>> How many databse fields with the same name i have into my model? Too
>>> much !!
>>>
>>> Thanks. Regards.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG Free Edition.
>>> Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date:
>>> 17.02.2006
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: ReportQuery bug 1.0.4
Posted by Jakob Braeuchi <jb...@gmx.ch>.
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())
{
Object[] data = (Object[]) iter.next();
System.out.println(data[0] + " called " + data[1]);
}
the sql looks quite ok:
SELECT A0.NUMBER,A1.NUMBER FROM PHONE_NUMBER A0 INNER JOIN CALLS A1 ON
A0.PHONE_NUMBER_ID=A1.PHONE_NUMBER_ID WHERE A1.NUMBER LIKE '%66%'
but the data retrieved from the resultset is wrong:
number and calls.numberCalled contain the same value :(
jakob
Jakob Braeuchi schrieb:
> 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, requesting "property_b" and "
>> classA.property_a". If database field names are the same in each table
>> for
>> property_a and property_b, surprise, that you believe the value of
>> property_b is the property_a one !!
>>
>> I looked to the generated query, and, awful, aliases are wrong.
>>
>> Anyone confirms ?
>>
>> OJB 1.0.4 (bug wasn't related in 1.0.1)
>>
>> How many databse fields with the same name i have into my model? Too
>> much !!
>>
>> Thanks. Regards.
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date:
>> 17.02.2006
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: ReportQuery bug 1.0.4
Posted by Jakob Braeuchi <jb...@gmx.ch>.
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, requesting "property_b" and "
> classA.property_a". If database field names are the same in each table for
> property_a and property_b, surprise, that you believe the value of
> property_b is the property_a one !!
>
> I looked to the generated query, and, awful, aliases are wrong.
>
> Anyone confirms ?
>
> OJB 1.0.4 (bug wasn't related in 1.0.1)
>
> How many databse fields with the same name i have into my model? Too much !!
>
> Thanks. Regards.
>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 17.02.2006
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org