That is the way it works now. I remember there is a reason for this, but can't remember the reason right now; I'm still a little tired.
Yep I closed 3 bugs last night at about 2 am.
Ok now I remember. You call User.getActivities() which causes the load. The code assumes that if you are getting the collection you plan on using it, which looks like a bad assumption in the light of this code.
When I rewrite this code next time, I'll think about your code. In the mean time, can you set the relation the other way arround:
That should not cause a load, but I can't be certain.
OK. Hadn't thought of that :)