Comments on kasper's source: JPA and the N+1 select problem

tag:blogger.com,1999:blog-1301643147176033927.post108689999356304173..comments2009-12-15T17:39:33.520+01:00Comments on kasper's source: JPA and the N+1 select problemKasper Sørensenhttp://www.blogger.com/profile/05310806961885711209noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1301643147176033927.post-57860041262363052602009-12-15T17:39:33.520+01:002009-12-15T17:39:33.520+01:00Yes, and that's also what Kenns article is abo...Yes, and that's also what Kenns article is about :-)Kasper Sørensenhttp://www.blogger.com/profile/05310806961885711209noreply@blogger.com

tag:blogger.com,1999:blog-1301643147176033927.post-45163243965016019772009-12-15T14:28:34.868+01:002009-12-15T14:28:34.868+01:00I believe you actually can avoid this by optimizin...I believe you actually can avoid this by optimizing, the persistence provider, it's described here http://www.javalobby.org/java/forums/m91885142.html (for hibernate), i bet openjpa and eclipselink has the same options. However JPA(1.0) itself might not have the ability to pass the information on to the provider so you might be forced to use specific annotations for that providerninomartinezhttp://www.blogger.com/profile/08251222580926489667noreply@blogger.com