Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (athena.apache.org: domain of clinton.begin@gmail.com
 designates 72.14.204.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:references:in-reply-to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language:message-id;
        b=fISDrXqiVT6sOamrDKiUdXzlO9cqnxqe/DSYcl/6F24gCJzz8ZowwPAtXwzkAPC3LHM6IIa3+vlEJtdo6q74ZRXzVq4wtpedroKHA7HubX0TmgWsUN4I0HQlaxxnH4BeU8MBTcpBsSp/IE8KQUQdKWR2UGnTYvZdQhIgdduQ3dM=
From: "Clinton Begin" <clinton.begin@gmail.com>
To: <user-java@ibatis.apache.org>,
	<lmeadors@apache.org>
References: <C3C6031E.3DA7%clamey@localmatters.com>
	 <1201716326.31524.1234151879@webmail.messagingengine.com>
	 <2f55db670801301036l5f890babl37e8ec52aea7559d@mail.gmail.com>
	 <1201719088.8102.1234163847@webmail.messagingengine.com>
	 <47a0cd3e.1f588c0a.217e.ffffb5e1@mx.google.com>
	 <c593b8750801301345v2f3b4fa4k2afa4cea697c2669@mail.gmail.com>
 <a10a823c0801301542macf064fv9c8d462ab0296630@mail.gmail.com>
In-Reply-To: <a10a823c0801301542macf064fv9c8d462ab0296630@mail.gmail.com>
Subject: RE: Exit out of rowHandler
Date: Wed, 30 Jan 2008 18:11:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AchjmeE7KmlKhCZJQZqs20quc8xNogAC/eyA
Content-Language: en-ca
Message-ID: <47a12054.17bc720a.27d4.750b@mx.google.com>

Hehe...

Well, considering how much effort I've always put into iBATIS being backward
compatible, why break tradition now?  ;-)  We can use an adapter and create
a new RowHandler interface.  

iBATIS 3.0 can merge them into one...as it won't be fully backward
compatible anyway.  

Clinton

-----Original Message-----
From: larry.meadors@gmail.com [mailto:larry.meadors@gmail.com] On Behalf Of
Larry Meadors
Sent: January-30-08 4:43 PM
To: user-java@ibatis.apache.org
Subject: Re: Exit out of rowHandler

Meh, it'll break compatibility, but it adds a great deal of useful
functionality for very little cost. In addition, the 'fix' is to add a
"return true;" to existing code. I wouldn't consider that particularly
onerous...unless you have like 1000 row handlers, in which case, you
probably *deserve* some pain. ;-)

I think it's a great idea.

Larry


On Jan 30, 2008 2:45 PM, Jeff Butler <jeffgbutler@gmail.com> wrote:
> I can't think of any other use for the return value, so I like the idea.
> The only drawback is that this will break existing row handlers.  This
could
> be an argument in favor of the two parameter approach - because it could
be
> an overloaded method.  Of course, any change to the interface is going to
> cause headaches for existing row handlers.  Maybe we should provide
adapter
> classes like AWT?
>
> <shudder>Did I just suggest using AWT as a model?</shudder>
>
> Jeff Butler
>
>
>
> On Jan 30, 2008 1:17 PM, Clinton Begin <clinton.begin@gmail.com> wrote:
>
> >
> > Hmmm... would it be horrible if the return value of handleRow() was a
> > boolean for "continue"?
> >
> > // don't mind the verbosity or any misplaced
> > // capital letters...thank you outlook
> > public boolean handleRow (Object valueObject) {
> >  boolean continue = true;
> >  if (someCondition) {
> >    continue = false;
> >  }
> >  return continue;
> > }
> >
> > I hate to suggest making use of the return value, because there is only
> > one...but it isn't used right now.  Is this the best use of the return
> > value? The alternative is to use a second parameter for controls...
> >
> > public void handleRow (ResultSetControl control, Object valueObject) {
> >  if (someCondition) {
> >    control.setContinue(false);
> >  }
> > }
> >
> > Sorry if this has already been discussed, it's more of a dev@ issue, but
> > since we're talking about it here...
> >
> > Thoughts?
> >
> > Clinton
> >
> >
> >
> >
>