> By the way this is the SELECT: > [7/26/11 17:49:29:904 CEST] 0000000e Query 3 openjpa.Query: > Trace: Executing query: SELECT b > FROM Bp b This trace line is as OpenJPA sees the object query. If you look at the corresponding SQL query that OpenJPA executes on the database, it will supply more evidence on what is going wrong. You can switch on SQL logging by <property name="openjpa.Log" value="SQL=TRACE"/>
> OpenJPA's FetchPlan functionality I could select the fields I would like > to load in a fine grained way. That is correct. I had also verified that the functional contract of fetch plan has not regressed. If you can supply a JUnit test with assertions, that will help further analysis. ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/Best-practice-Using-fetch-groups-or-a-simple-DTO-tp6598057p6622886.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
