It looks like Mike just took ownership of OPENJPA-1001. My guess is that the first approach at resolving this issue will be to resolve this specific issue, and not the whole QuerySQLCache re-architecture. I would monitor that JIRA and comment directly on that JIRA.
Thanks, Kevin On Thu, Aug 13, 2009 at 9:43 AM, ljnelson <[email protected]> wrote: > > On Thu, Aug 13, 2009 at 10:19 AM, Kevin Sutter (via Nabble) < > [email protected]<ml-user%[email protected]> > <ml-user%[email protected]<ml-user%[email protected]> > > > > wrote: > > > From the description in the JIRA [1], it seems that this problem is > related > > > > to the QuerySQLCache [2] that is "on" by default. > > > First of all, my apologies for not realizing initially that my problem > reduced to the same problem. It looked initially like it was coming from > an > unrelated area, via a different code path. Obviously it was not. Sorry > about that. > > As a workaround, you > > should be able to turn off this property and get around the problem. > > > Indeed, that "fixed" it. I look forward to the 2.0 fix being backported to > the 1.3 line. > > Best, > Laird > > -- > View this message in context: > http://n2.nabble.com/OPENJPA-1001-tp3437948p3438431.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
