* The default should be fetch="select" for collections, what should the default be for to-one associations? I suppose that purely for backward compatibility purposes we need fetch="auto|join|select", where auto is the default, and chooses "select" for a lazy-enabled class.
Keep the "auto" and the "global max_fetch_depth". However, we should think about allowing cartesian products if the users whishes so and allow several FETCH in HQL, too. This means that "auto" and "max_fetch_depth" also works for -to-many. I know how difficult this can be to explain, so I'm not 100% sure about this. It would feel more complete if you had this feature for some small tables with few rows.
* Should we provide XSLT stylesheets to transform 2.x mapping to 3.0 mappings, rather than providing backward compatibility at the mapping document level, by adding default-lazy and continuing to support the outer-join attribute?
As Emmanuel and Max already said, we can do it if we are careful and communicate this properly. So far global search & replace is good enough for migration, that is nice to have. We should keep full backward compatibility (which works nicely with your proposal Gavin) and then remove some attributes in 3.1. We'd have an additional buffer to make decisions and can see how the changes are accepted. I wouldn't be surprised if we make some more modifications to this in release candidates.
-- Christian Bauer +49 171 455 66 53 callto://christian-bauer
Hibernate [EMAIL PROTECTED] http://hibernate.org
JBoss Inc [EMAIL PROTECTED] http://jboss.com
------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
