I have a detached A which has a not-cascaded List of B's that were eager fetched in the previous transaction.
Now when I try to merge this A, hibernate replaces all B's with a proxy but leaves the B List alone, which surprises me, since it's not cascaded.
I expected it to replace the B List with an uninitialized list, since it's not cascaded. Is there any way I can configure it so it does replaces the B list with an unitialized list during a merge of A?

After some debugging, it turns out it does replace the B list with an uninitialized list during the merge of A.

However, because the B List is intialized when starting the merge of A, it decides to load all B's with n + 1 queries from the database. Why?
It doesn't actually use those B's, although it does crash if one of those B's no longer exists (and I don't want it to crash on that). Is there any way I can turn off that useless loading?

Thanks for any help :)

I've created a testcase patch which clearly demonstrates the inconsistency:

http://opensource.atlassian.com/project ... se/EJB-347