-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roland Carlsson wrote:
Thanks, that solved the problem. I thought that I could have my own
fetch-size but I has now understood that Integer.MIN_VALUE is the only size
that is accepted.
Regards
Roland Carlsson
The fetch-size setting makes sense for drive
on" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 11, 2003 2:17 PM
Subject: Re: Large resultset
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Roland Carlsson wrote:
> > Hi!
> > I have a query that returns a resultset of 70 mb. I&#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roland Carlsson wrote:
Hi!
I have a query that returns a resultset of 70 mb. I'd somehow would like
J/Connector to fetch only small pieces using Statement.setFetchSize but it
still get the whole ResultSet at once and then I get an OutOfMemoryError.
Is i
Hello and thanks for your answer!
If I have understood correctly LIMIT will only return as many row as the
limit. I need all rows, but I can't handle them all at once. In JDBC there
are a method to "stream" the resultset into small portions and when the end
of the portion is reached it automatical
ECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 11, 2003 1:08 PM
Subject: Re: Large resultset
>
>
> > I have a query that returns a resultset of 70 mb. I'd somehow would like
> > J/Connector to fetch only small pieces using Statement.setFetchSize but
> it
>
> I have a query that returns a resultset of 70 mb. I'd somehow would like
> J/Connector to fetch only small pieces using Statement.setFetchSize but
it
> still get the whole ResultSet at once and then I get an OutOfMemoryError.
> Is it a bug in setFetchSize? Does J/Connector ignore it? Have I to
