You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Karen Koch (JIRA)" <ib...@incubator.apache.org> on 2005/03/22 17:19:29 UTC
[jira] Created: (IBATIS-92) Child object created when no child record exists (due to nullValue=)
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (IBATIS-92) Child object created when no child record exists (due to nullValue=)
Posted by "Clinton Begin (JIRA)" <ib...@incubator.apache.org>.
[ 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
[jira] Commented: (IBATIS-92) Child object created when no child record exists (due to nullValue=)
Posted by "Iwao AVE! (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATIS-92?page=comments#action_12355589 ]
Iwao AVE! commented on IBATIS-92:
---------------------------------
I think this should be logged as 'Bug' not as a 'New Feature'.
I had the same problem in version 2.1.5.582.
Is there any plan for a fix or workaround?
> 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