Hi
I would like to use something like:
SELECT * FROM Device
WHERE "id"=#identifier#
provided, the input xml would be something like:
1
my-name
I went through the documentation and searched the forum. But in vain.
Is this supported? Is this possible?
Your help
I will be out of the office starting 04/13/2009 and will not return until
04/14/2009.
I will be glad to answer your email when I return. Thanks.
I have the following:
insert into thing (thing_id, animal, mineral, vegetable)
values (
#thingId#,
#animal:BOOLEAN:False#,
#mineral:BOOLEAN:False#,
#vegetable:BOOLEAN:False#
)
When iBatis executes the above an exception is thrown:
com.ibatis.common.jdbc.exc
can you turn on logging to see what values ibatis is sending to the insert?
On Mon, Apr 13, 2009 at 5:49 PM, Gavin McLeod wrote:
> I have the following:
>
>
> insert into thing (thing_id, animal, mineral, vegetable)
> values (
> #thingId#,
> #animal:BOOLEAN:False#,
> #miner
Null value replacement makes my head hurt.
It bit me, because it worked exactly the OPPOSITE of what I expected.
When doing a select, if the database value is null, ibatis will use
the replacement value for your result.
When doing an insert, if the parameter property is the replacement
value, it
That¹s why I¹ve never managed to get it to work. Can I suggest that for the
next version the logic be reversed on inserts. It¹s not a big deal as it
makes sense to implement this type of logic in the business layer but for
simple projects it might be beneficial.
Z.
>
> Null value replacement mak
I've done one better... iBATIS 3 does not support null value replacement at
all.
Cheers then. :-)
Clinton
On Mon, Apr 13, 2009 at 8:51 PM, Zoran Avtarovski
wrote:
> That’s why I’ve never managed to get it to work. Can I suggest that for
> the next version the logic be reversed on inserts. It’
oh right this "feature" was made for the times when you have a nullable
column in a DB, and for some strange reason, you only have a non-nullable
java type like a primitive int.
On Mon, Apr 13, 2009 at 7:59 PM, Larry Meadors wrote:
> Null value replacement makes my head hurt.
>
> It bit me, beca
Yes, that's exactly right Nathan. I like to believe the world has changed,
and that if we're in such a situation again today, we can just change the
data type in the app. :-)
Clinton
On Mon, Apr 13, 2009 at 10:08 PM, Nathan Maves wrote:
> oh right this "feature" was made for the times when you