Well, I still think that this is almost always a Bad Thing, but it is now possible to configure (exactly one) collection to be loaded by outer join in the mapping file.
This will affect the fetching beviour for * load() * Criteria queries * lazy association access It does not affect the behaviour of HQL queries, which provide the FETCH clause. Implementing this feature did allow me to make some nice design improvements to OuterJoinLoader. Theres still some extra thought to go on the code which decides exactly when to do the outer join and when not to. This feature could result in some extremely deep fetching, so I'm thinking of adding a hibernate.max_outerjoin_fetch_depth property or something. All in v21branch. ********************************************************************** Any personal or sensitive information contained in this email and attachments must be handled in accordance with the Victorian Information Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988 (Commonwealth), as applicable. This email, including all attachments, is confidential. If you are not the intended recipient, you must not disclose, distribute, copy or use the information contained in this email or attachments. Any confidentiality or privilege is not waived or lost because this email has been sent to you in error. If you have received it in error, please let us know by reply email, delete it from your system and destroy any copies. ********************************************************************** ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
