TIS that
isn't immediately apparent. And no, I can't use Abator on this project.
:)
-D
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Larry Meadors
Sent: Tuesday, December 12, 2006 9:33 AM
To: user-java@ibatis.apache.org
Subject: Re: Using parameterM
a generally good, forward-thinking
practice...Do you still disagree?
-D
--
*From:* Jeff Butler [mailto:[EMAIL PROTECTED]
*Sent:* Monday, December 11, 2006 5:15 PM
*To:* user-java@ibatis.apache.org
*Subject:* Re: Using parameterMaps
Several things...
1. map is OK
ors
Sent: Tuesday, December 12, 2006 9:33 AM
To: user-java@ibatis.apache.org
Subject: Re: Using parameterMaps
I wouldn't do it because I am a minimalist and it adds more mess to
the code, but if you sleep better at night knowing it's there, go for
it. :)
Hopefully you'll have a mainta
TED]
Sent: Monday, December 11, 2006 5:15 PM
To: user-java@ibatis.apache.org
Subject: Re: Using parameterMaps
Several things...
1. map is OK - it is a predefined type alias
2. java.util.HashMap is OK also
3. When using parameter maps, you must specify question marks in the SQL
instead of property n
onday, December 11, 2006 5:15 PM
To: user-java@ibatis.apache.org
Subject: Re: Using parameterMaps
Several things...
1. map is OK - it is a predefined type alias
2. java.util.HashMap is OK also
3. When using parameter maps, you must specify question marks in the SQL
instead of property names. T
As Jeff said, remember is that anywhere that you specify a result or
parameter class, you can use a type alias (which is what "map" and
"hashmap" are - type aliases for "java.util.Map" and
"java.util.HashMap"). The user guide lists most of the type aliases,
and you can also define your own.
Also,
Several things...
1. map is OK - it is a predefined type alias
2. java.util.HashMap is OK also
3. When using parameter maps, you must specify question marks in the SQL
instead of property names. This is likely the cause of your problem. For
this reason, I recommend that you forego the use of ex
