So you have desc in two places? This is getting more confusing. Maybe post
the expected result set and the classes you're mapping it to.
Clinton
On Tue, Apr 6, 2010 at 9:09 PM, Viv Kapadekar <vi...@peoplepowerco.com>wrote:
> Yeah actually to make it more clear Class X also has desc. So its really:
> Class X {
> String id
> String desc
> List<Y> b
> }
> If index is null the desc is applicable for X and when its not null it
> should be applicable to X.
>
> --V
>
> On Apr 6, 2010, at 7:21 PM, Clinton Begin wrote:
>
> If iBATIS finds ANY values for the mapped properties, it will create the
> object. Is it possible that the desc column is populated even when the
> index is null?
>
> On Tue, Apr 6, 2010 at 7:52 PM, Viv Kapadekar <vi...@peoplepowerco.com>wrote:
>
>> Hi
>> I have a Class X containing a List of Class Y
>>
>> Class X {
>> String a
>> List<Y> b
>> }
>>
>> Class Y {
>> String index
>> String desc
>> }
>>
>> The resultMap I have is
>>
>> <resultMap id="someID" type="X">
>> <id property="a" column="id"/>
>> <collection property="b" ofType="Y">
>> <id property="index" column="index"
>> />
>> <result property="desc"
>> column="desc"/> -->
>> </collection>
>> </resultMap>
>>
>> This is fine, but I don't want the resulting X to have the collection b
>> set, if the "index" value is null. If index is null, even the value of b in
>> X should be null. I tried using <discriminator> and also tried creating a
>> separate sql, but no luck. Any ideas?
>>
>> -V
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
>> For additional commands, e-mail: user-java-h...@ibatis.apache.org
>>
>>
>
> ---------------------------------------------------------------
> Viv Kapadekar
> vi...@peoplepowerco.com
>
>
