ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Hillyerd <ja...@hillyerd.com>
Subject Re: Problem with avoiding N+1 queries on complex collection property
Date Thu, 02 Feb 2006 05:06:52 GMT
I think an empty List would make more sense than null, but that's
besides the point.  It's always setting it to null, even when there
are four phone numbers.  I get no phone numbers period when I try to
avoid N+1.


On 2/1/06, Brandon Goodin <brandon.goodin@gmail.com> wrote:
> I'm curious here. If you want a List to always be there wouldn't it
> make sense to instantiate a list and set it in the constructor of your
> Client object? If you do this does ibatis set it to null when there
> are no phone numbers? I would prefer that ibatis not make assumptions
> about what default values that you want set on your object. If ibatis
> is forcing it to null then i think that should be considered a bug and
> entered into a bug report. If it does not then I think that it is the
> developer's job insure defaults to be set.
> Brandon Goodin

James A. Hillyerd <james@hillyerd.com>
Chief Technical Officer - ActiveRain Corp

View raw message