Hi Kevin, I added that property and it fixed the problem.
Kind regards, Enrico Kevin Sutter wrote: > > Egoosen2, > One new feature that went into 1.2.0 was the ability to cache some of the > generated sql on common queries. Previous to this change, every query or > findBy operation required the same sql to be generated over and over > again. > It may be possible that the caching is picking up the wrong sql for the > scenario that you describing. As a quick test, could you try running with > this sql query cache turned off? The property follows: > > openjpa.jdbc.QuerySQLCache = false > > If you could try this and let us know the results, it will help with > narrowing down the scope of the problem. > > Thanks! > Kevin > > -- View this message in context: http://n2.nabble.com/OpenJPA-1.2.0-Bug-on-FetchType.EAGER-tp1100274p1100906.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
