Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 16086 invoked from network); 3 Feb 2010 21:00:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Feb 2010 21:00:44 -0000 Received: (qmail 4404 invoked by uid 500); 3 Feb 2010 21:00:43 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 4372 invoked by uid 500); 3 Feb 2010 21:00:43 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 4360 invoked by uid 99); 3 Feb 2010 21:00:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2010 21:00:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of clinton.begin@gmail.com designates 209.85.212.53 as permitted sender) Received: from [209.85.212.53] (HELO mail-vw0-f53.google.com) (209.85.212.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2010 21:00:33 +0000 Received: by vws10 with SMTP id 10so24238vws.12 for ; Wed, 03 Feb 2010 13:00:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=sHh4ehfRSxEPRmOP3v9xfbtD8GL2ovM2eSgogaXUyNk=; b=C3595Y/xW+VeOqTMPS0GdfMpbTVa1XbWZbnw39FTMSakgMyXdFwaN8H+TxINALp/Br vmqICJAJ5Uhzeur1xJetNEnjDKUH3wwobNLTVscmtmvzX6wknVLoVmQCNCwtsrnYw3lz SY7l3Kg1kBwElWdYnn9OwtzttdMr2VMt9ubAM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=g8grxFRkjChsJq7xdog60mJcYgcMX//bpRnmxD23XznD0ONJ5h7hX34SSzsEq+RrV4 FALN3pdERzD31/Bl0Wu19ayvX/HX3x1vDKeqAafmj8ssEyoLcIbo6mRTohHfdYQtSsoD 37AZ/2Ud9hj9WkusQCanI4UTR0cOGwc2lbjns= MIME-Version: 1.0 Received: by 10.220.121.139 with SMTP id h11mr116712vcr.87.1265230812338; Wed, 03 Feb 2010 13:00:12 -0800 (PST) In-Reply-To: References: <81cfe9551002020613n4fabb9e9ha824154762df2b9b@mail.gmail.com> <16178eb11002020625n431fc10q9849496b5b29bc5a@mail.gmail.com> <81cfe9551002030916j1e0aee57lb9bc425570de2ca7@mail.gmail.com> <4173dc211002031219g418b4320tbc46e3fb8c872930@mail.gmail.com> <4173dc211002031232w3e112087i14e58d2c99a4063c@mail.gmail.com> Date: Wed, 3 Feb 2010 14:00:12 -0700 Message-ID: <16178eb11002031300u52c303c2ob4ea206c62fb30d9@mail.gmail.com> Subject: Re: Mapper parsing problem From: Clinton Begin To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=0016369f9cfd20da21047eb88143 X-Virus-Checked: Checked by ClamAV on apache.org --0016369f9cfd20da21047eb88143 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This was actually a very serious consideration for us. I personally like this design a lot. FWIW: Parameter maps are in iBATIS 3, but the DTD disables the element. Primary reason is that it still works exactly like iBATIS 2, which is not based on named parameters as you've suggested. Before adding it back, I want to ensure that it works this way, but it's a bit of work to get it there. Clinton On Wed, Feb 3, 2010 at 1:54 PM, Daryl Stultz wrote: > > > On Wed, Feb 3, 2010 at 3:32 PM, Simone Tripodi = wrote: > >> Forgot to say that, of course, there are cons, like in the sample below: >> >> I misread your first post and was thinking you wanted something like thi= s: > > > resultMap=3D"departmentResultMap"/> > insert into users (id, username, password, department) > values (#{id}, #{username}, #{password}, #{department}) > > > I'm totally mixing your examples up, but the point is "parameterDef" just > defines the nature of the parameter, #{department} just applies the value= in > the right spot. Maybe that's worse, I don't know! > > -- > Daryl Stultz > _____________________________________ > 6 Degrees Software and Consulting, Inc. > http://www.6degrees.com > mailto:daryl@6degrees.com > --0016369f9cfd20da21047eb88143 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This was actually a very serious consideration for us.=A0 I personally like= this design a lot.=A0

FWIW:=A0 Parameter maps are in iBATIS 3, but= the DTD disables the element.=A0 Primary reason is that it still works exa= ctly like iBATIS 2, which is not based on named parameters as you've su= ggested.=A0 Before adding it back, I want to ensure that it works this way,= but it's a bit of work to get it there.

Clinton

On Wed, Feb 3, 2010 at 1:54 P= M, Daryl Stultz <daryl@6degrees.com> wrote:


On Wed, Feb 3, 2010 at= 3:32 PM, Simone Tripodi <simone.tripodi@gmail.com> w= rote:
Forgot to say that, of course, there are cons, like in the sample below:
I misread your first post and was thinking you = wanted something like this:

<= insert id=3D=94insertUser=94 parameterType=3D=94User=94 >
=A0=A0 <parameterDef name=3D"department" mode=3D&= quot;OUT" jdbcType=3D"CURSOR"=A0javaTy= pe=3D"Department" resultMap=3D"departmentResultMap"/>= ;=A0
=A0=A0 =A0insert into users (id, username, password, department)
=A0=A0 = =A0values (#{id}, #{username}, #{password}, #{department})
</insert&g= t;

I'm totally mixing your examples up, but the point= is "parameterDef" just defines the nature of the parameter, #{de= partment} just applies the value in the right spot. Maybe that's worse,= I don't know!=A0

--
Daryl Stultz
_________________________= ____________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto= :daryl@6degrees.com=

--0016369f9cfd20da21047eb88143--