>From this exchange, do we have a problem with the informational message?
*36703 IM INFO [main] openjpa.Query - This query on type "class mi.NominaEmpleador" must load the entire candidate class extent and evaluate the query in-memory. This may be very slow. The query must be executed in memory because OpenJPA is configured with IgnoreCache=false and FlushBeforeQueries=false and there are dirty instances that may affect the query's outcome in the cache.* In this message, a property of "IgnoreCache" is specified, but Pinaki's reply (and hantone's confirmation) used the property "IgnoreChanges" to get around the problem. Also, it sounds like hantone tried setting the other property (FlushBeforeQueries) to true without any luck. Do we have some cleanup required either in the message or in the processing of in-memory queries so that we're consistent? Thanks, Kevin On Wed, Jul 28, 2010 at 3:44 PM, hantone <[email protected]> wrote: > > Hi Pinake! > > I tried b) and it worked perfectly! > > That was exactly what I was looking for! > > Thank You very much! Take care! > > Horacio A Antonelli > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Performace-Question-tp5343744p5346335.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
