Lazy loading is now disabled by default in trunk. It actually was already depending on how you configured it. But no matter, now it is for sure.
Clinton On Mon, Oct 12, 2009 at 8:03 PM, Clinton Begin <clinton.be...@gmail.com>wrote: > In a nutshell, if a nested Statement or ResultMap is used to populate a > non-collection (List) field: > * If all columns mapped are null, the field should be null as well. > * This should be consistent with lazy loading enabled or disabled. > > If it's a collection type (List), then: > > * If all columns mapped are null, the field should be set to an empty > collection. > * This should be consistent with lazy loading enabled or disabled. > > Cheers, > Clinton > > On Mon, Oct 12, 2009 at 2:15 PM, Guy Rouillier <guyr-...@burntmail.com>wrote: > >> Clinton Begin wrote: >> >>> Only collection properties should be populated when you refer to them >>> (empty collections). But complex association types should be null. >>> >> >> Sorry, I'm not comprehending the implications of your last statement. I >> have complex (non-primitive) object types in my associations. Are you >> saying that from Beta 4 onwards, all such associations will not be populated >> if lazy loading is enabled? So if you have non-primitive associations, then >> you must disable lazy loading? >> >> Thanks. >> >> >> -- >> Guy Rouillier >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org >> For additional commands, e-mail: user-java-h...@ibatis.apache.org >> >> >
