[ http://issues.apache.org/jira/browse/IBATIS-92?page=all ]
Clinton Begin closed IBATIS-92:
-------------------------------
Resolution: Duplicate
duplicate of ibatis-213
> Child object created when no child record exists (due to
> nullValue=<somevalue>)
> -------------------------------------------------------------------------------
>
> Key: IBATIS-92
> URL: http://issues.apache.org/jira/browse/IBATIS-92
> Project: iBatis for Java
> Type: New Feature
> Components: SQL Maps
> Versions: 2.0.9b
> Reporter: Karen Koch
> Priority: Minor
>
> Child object created when no child record exists:
> One resultMap has a List property in it. The List property has a
> resultMap indicated. The resultMap of the child object (List
> property) has nullValue=<somevalue> specified for one or more
> properties. A query written with a LEFT JOIN returns one parent
> record but no child records. One would expect that one parent object
> would be created, but that the list property would remain as an empty
> list (no child objects created). It *seems* that due to the
> nullValue=<somevalue> specifiers, one child object is being created anyhow.
> This issue makes it impossible (?) to support saving (some) null values to
> the database for a child record as needed while not unnecessarily creating a
> bogus child object on a select.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
