I had the same issue, and it's fixed in the latest version of iBatis. You just need to add a "notNullColumn=true" to the resultMap.
On Tue, Jan 6, 2009 at 8:01 PM, Jeff Butler <jeffgbut...@gmail.com> wrote: > See here: > > http://issues.apache.org/jira/browse/IBATIS-375 > > Looks like a fix for this is in 2.3.4. > > Jeff butler > > > On Tue, Jan 6, 2009 at 3:42 PM, Hugh Ross <hh4r...@gmail.com> wrote: >> >> We are testing some sqlMaps to avoid the N+1 Selects problem that include >> OUTER JOINs. Since nulls are coming back in the Result Sets, we are seeing >> pojos created with all nulls. Testing with iBatis 2.3.4. >> >> I don't recall seeing this problem mentioned before, but I can't believe no >> one else has hit it -- any suggestions for avoiding the null pojo objects >> (other than deleting them after creation)? >> >> Thanks... >
