Thanks Matthew, for an excellent elaboration on the fundamental idea behind fetch plans.
eBean sure looks like an interesting development in object persistence . The mechanics to specify fetch path varies in OpenJPA and eBean -- but they are aiming for very similar goal which is to isolate query filter specification (the where clause) from the access path -- that SQL traditionally combined and current JPA continues the tradition via its FETCH JOIN. I especially liked its idea about AutoFetch -- but missed the OpenJPA's ability to configure Fetch Plans both at design-time and at runtime (but I have not looked deep enough in eBean). The idea of fetch paths i.e. ability to customize the sub-graph rooted at instances selected by a query filter is here to stay and has now gained enough prominence for being a candidate for standardization. I hope many of your experience in this area be heard when new JPA spec comes out. btw, Matthew, on the result shape, you may like the ResultShape constructs in OpenJPA :) ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/OpenJPA-rock-and-fetch-plan-is-a-killing-feature-tp5978322p5981839.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
