From: Brad C. <bra...@wo...> - 2002-11-21 21:06:42
|
i think the reason that the default value for lazy is false is that lazy loading imposes some restrictions on the usage of mapped classes, eg. = the session must still be open when u attempt to access the lazily loaded collection. i think your mapping file should stay the same between dev & production, otherwise u might introduce errors that u would probably have caught in development. brad ----- Original Message ----- From: "Donnerstag, Juergen" <jue...@ed...> To: <hib...@li...> Sent: Wednesday, November 20, 2002 8:49 PM Subject: [Hibernate] default for lazy > > The documentation states that the default value for lazy is defined as > false. This is ok, as possible problems are detected more easily = (earlier) > this way. Unfortunately this means you have to manually (or by means = of > XSLT) modify all lazy-attributes in all XML-mappings for production = like > systems. What do you think about a property e.g. hibernate.lazy which > defines the default. If not set or defined, false would be still be = used. > Only relations which are meant to be lazy=3Dfalse during production = would have > to set explicitly. > > regards > Juergen > > > ------------------------------------------------------- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > _______________________________________________ > hibernate-devel mailing list > hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > |