ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Butler (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Commented: (IBATIS-557) Error referencing iterable fields as properties of a dynamic SQL statement
Date Wed, 03 Dec 2008 15:25:44 GMT

    [ https://issues.apache.org/jira/browse/IBATIS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652829#action_12652829
] 

Jeff Butler commented on IBATIS-557:
------------------------------------

Please try iBATIS version 2.2 or higher.  We did not support nested iterables until that version
and we made a lot of improvements in how the tags worked.

> Error referencing iterable fields as properties of a dynamic SQL statement
> --------------------------------------------------------------------------
>
>                 Key: IBATIS-557
>                 URL: https://issues.apache.org/jira/browse/IBATIS-557
>             Project: iBatis for Java
>          Issue Type: Bug
>          Components: SQL Maps
>    Affects Versions: 2.1.7
>            Reporter: aaron pieper
>
> iBatis is throwing an exception when I try to use an iterable field as the property to
a nested isNull or isNotNull statement. My SQL map looks something like this:
> ------------------------------------------------------------
> SELECT *
> FROM foo
> WHERE
> <iterate property="searchCriteria" conjunction=" OR ">
> 	<isNotNull property="searchCriteria[]">
> 		foo.bar=#searchCriteria[]#
> 	</isNotNull>
> 	<isNull property="searchCriteria[]">
> 		foo.bar is null
> 	</isNull>
> </iterate>
> ------------------------------------------------------------
> This produces a NumberFormatException, caused by "searchCriteria[]" being specified as
a property. If I change the property to "searchCriteria" (without the braces) instead, then
I don't get the exception (but the resulting behavior is incorrect.)
> This looks similar to the tracker IBATIS-42 (http://issues.apache.org/jira/browse/IBATIS-42)
but that particular tracker was marked as fixed in version 2.1.0, and I'm still seeing this
problem in 2.1.7.597.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message