From what I understand the effect is the same, but the EJB3 engine generates
different SQL-code. When you eager-load all the data is fetched in one big
SQL-JOIN query. A lazily fetched relation is queried in a separate SQL query.
If you always need the related entities it should be faster to
There is a problem with having multiple eager many relationships within the
same bean.
http://jboss.org/index.html?module=bbop=viewtopict=76796
Alex
ejb3workshop.com
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3939221#3939221
Reply to the post :
Thanks *very* much for the info, everyone - very helpful!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3939416#3939416
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3939416
So, it's been a couple of days and noone has answered me yet.
Is pre-loading a lazily-fetched collection not essentially the same as just
using eager fetching?
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937243#3937243
Reply to the post :