You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Michael Vorburger <mv...@odyssey-group.com> on 2008/10/02 15:41:28 UTC
RE: OpenJPA 1.2.0 Bug on FetchType.EAGER
Hello,
Just FYI: We also just ran into this after switching from 1.1.0 to
1.2.0... As described in earlier posts in this thread, wrong SQL was
used when accessing a collection field defined in a superclass from two
different subclasses. Using openjpa.jdbc.QuerySQLCache = false made the
problem go away.
Wouldn't this warrant the release of a 1.2.1 fix?
Regards,
Michael
-----Original Message-----
From: egoosen [mailto:egoosen2@metropolitan.co.za]
Sent: mardi, 30. septembre 2008 11:19
To: users@openjpa.apache.org
Subject: Re: OpenJPA 1.2.0 Bug on FetchType.EAGER
Hi,
Sorry for late reply, been snowed under.
I tested with 1.3.0-SNAPSHOT and it works fine.
Thank you guys!
Enrico
catalina wei-2 wrote:
>
> Enrico,
> I have committed Fay's patch under trunk r699156. Could you please
> extract latest code and verify if it fix the problem?
> Thanks.
> Catalina
>
> On Fri, Sep 26, 2008 at 12:10 AM, egoosen
> <eg...@metropolitan.co.za>wrote:
>
>>
>> Excellent. Thanks Fay.
>>
>>
>> Fay Wang wrote:
>> >
>> > Thank you, Enrico. I am able to reproduce the problem now. Will
>> > post a patch to JIRA-731 soon.
>> >
>> > -Fay
>> >
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/OpenJPA-1.2.0-Bug-on-FetchType.EAGER-tp1100274p1
>> 120214.html Sent from the OpenJPA Users mailing list archive at
>> Nabble.com.
>>
>>
>
>
--
View this message in context:
http://n2.nabble.com/OpenJPA-1.2.0-Bug-on-FetchType.EAGER-tp1100274p1128
433.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
____________________________________________________________
� This email and any files transmitted with it are CONFIDENTIAL and intended
solely for the use of the individual or entity to which they are addressed.
� Any unauthorized copying, disclosure, or distribution of the material within
this email is strictly forbidden.
� Any views or opinions presented within this e-mail are solely those of the
author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
� An electronic message is not binding on its sender. Any message referring to
a binding engagement must be confirmed in writing and duly signed.
� If you have received this email in error, please notify the sender immediately
and delete the original.
Re: OpenJPA 1.2.0 Bug on FetchType.EAGER
Posted by Michael Dick <mi...@gmail.com>.
Hi Michael,
I agree, we'll have to address this issue in 1.2.x - release to release
regressions need to be cleaned up. I'm going to target OpenJPA-731 for that
release.
Thanks for pointing it out to us.
-mike
On Thu, Oct 2, 2008 at 8:41 AM, Michael Vorburger <
mvorburger@odyssey-group.com> wrote:
> Hello,
>
> Just FYI: We also just ran into this after switching from 1.1.0 to
> 1.2.0... As described in earlier posts in this thread, wrong SQL was
> used when accessing a collection field defined in a superclass from two
> different subclasses. Using openjpa.jdbc.QuerySQLCache = false made the
> problem go away.
>
> Wouldn't this warrant the release of a 1.2.1 fix?
>
> Regards,
> Michael
>
>
> -----Original Message-----
> From: egoosen [mailto:egoosen2@metropolitan.co.za]
> Sent: mardi, 30. septembre 2008 11:19
> To: users@openjpa.apache.org
> Subject: Re: OpenJPA 1.2.0 Bug on FetchType.EAGER
>
>
> Hi,
>
> Sorry for late reply, been snowed under.
> I tested with 1.3.0-SNAPSHOT and it works fine.
>
> Thank you guys!
> Enrico
>
>
> catalina wei-2 wrote:
> >
> > Enrico,
> > I have committed Fay's patch under trunk r699156. Could you please
> > extract latest code and verify if it fix the problem?
> > Thanks.
> > Catalina
> >
> > On Fri, Sep 26, 2008 at 12:10 AM, egoosen
> > <eg...@metropolitan.co.za>wrote:
> >
> >>
> >> Excellent. Thanks Fay.
> >>
> >>
> >> Fay Wang wrote:
> >> >
> >> > Thank you, Enrico. I am able to reproduce the problem now. Will
> >> > post a patch to JIRA-731 soon.
> >> >
> >> > -Fay
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://n2.nabble.com/OpenJPA-1.2.0-Bug-on-FetchType.EAGER-tp1100274p1
> >> 120214.html Sent from the OpenJPA Users mailing list archive at
> >> Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/OpenJPA-1.2.0-Bug-on-FetchType.EAGER-tp1100274p1128
> 433.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>
> ____________________________________________________________
>
> • This email and any files transmitted with it are CONFIDENTIAL and
> intended
> solely for the use of the individual or entity to which they are
> addressed.
> • Any unauthorized copying, disclosure, or distribution of the material
> within
> this email is strictly forbidden.
> • Any views or opinions presented within this e-mail are solely those of
> the
> author and do not necessarily represent those of Odyssey Financial
> Technologies SA unless otherwise specifically stated.
> • An electronic message is not binding on its sender. Any message referring
> to
> a binding engagement must be confirmed in writing and duly signed.
> • If you have received this email in error, please notify the sender
> immediately
> and delete the original.
>