Lamey [mailto:[EMAIL PROTECTED]
Sent: January-30-08 6:32 PM
To: user-java@ibatis.apache.org
Subject: RE: Exit out of rowHandler
Yes, please keep backwards compatability within minor releases.
-Original Message-
From: Clinton Begin [mailto:[EMAIL PROTECTED]
Sent: Wed 1/30/2008 6:11 PM
To: user
Yes, please keep backwards compatability within minor releases.
-Original Message-
From: Clinton Begin [mailto:[EMAIL PROTECTED]
Sent: Wed 1/30/2008 6:11 PM
To: user-java@ibatis.apache.org; [EMAIL PROTECTED]
Subject: RE: Exit out of rowHandler
Hehe...
Well, considering how much effort
Clinton
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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
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* so
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
ECTED]
Sent: January-30-08 11:51 AM
To: ibatis user
Subject: Re: Exit out of rowHandler
Here is the code that is causing the memory leak:
sqlMapClient.queryWithRowHandler("getSomeList", queryObject, this);
public void handleRow (Object valueObject)
{
;
}
As you can see,
; > > > the ibatis xml file eliminated 90% of the memory leak. Also, straight
> > > > forward query from one table that returns millions of rows from ibatis
> > > > yielded NO memory leaks. So there's something about joins but more
> > > > significantly - group by clause. My guess is
of a Map to implement the groupBy clause and is simply
> letting
> > > it grow indefinitely.
> > >
> > > One more bit of information. Just throwing an Exception alone in the
> > > "handleRow" will not get you out of the "loop". I had to iss
; > "sqlMap.endConnection()" to force the calling routine within ibatis to
> > throw a NullPtrException in order to exit. If anybody has any other
> > ideas, I'd appreciate it. It does work but it's very ugly.
> >
> > On Tue, 29 Jan 2008 20:24:13 -0700, &qu
If anybody has any other
> ideas, I'd appreciate it. It does work but it's very ugly.
>
> On Tue, 29 Jan 2008 20:24:13 -0700, "Chris Lamey"
> <[EMAIL PROTECTED]> said:
>> I have processed millions of rows with a rowhandler and no memory leaks
>
said:
> I have processed millions of rows with a rowhandler and no memory leaks
> in several different applications.
>
>
> -Original Message-
> From: Harvey Kim [mailto:[EMAIL PROTECTED]
> Sent: Tue 1/29/2008 5:23 PM
> To: ibatis user
> Subject: Re: Exit out of r
I have processed millions of rows with a rowhandler and no memory leaks in
several different applications.
-Original Message-
From: Harvey Kim [mailto:[EMAIL PROTECTED]
Sent: Tue 1/29/2008 5:23 PM
To: ibatis user
Subject: Re: Exit out of rowHandler
Thanks, I'm currently throwi
Thanks, I'm currently throwing an exception but that is really ugly. I
was hoping for more "graceful" solution. But I guess I can live with
it. Oh, and "Cancel" button won't be a problem - I got that covered.
Another thing - I've issued this question few months back but there ws
no reply. Does
On Jan 29, 2008 4:34 PM, Harvey Kim <[EMAIL PROTECTED]> wrote:
> Anybody know how to gracefully exit out of "handleRow" method? Before
> anybody suggests using "queryFor*" methods, I need to be able to query
> for potentially 12 million rows. It's a straight download to an excel
> file so nothing
14 matches
Mail list logo
