Java.lang.outOfMemoryError on large ResultSet

MySQL 5.0 Alpha Jdbc Driver: Connector J OS: Windows 2000 Professional Table Size 1 Mil. Records. Table Structure: Table1 logid - autoincrement int(11) Timestamp - timestamp Timestamp2 - timestamp Tag - varchar(15) Query/Code: --- PreparedStatement pst = con.prepareStatement(Select

Re: Java.lang.outOfMemoryError on large ResultSet

The problem is not the memory on the database server, but on the client running the JDBC connection. Seems that when you retrieve the result it is trying to store everything in memory at once. Here is some info from the mysql docs that looks like it pertains, see

Re: Java.lang.outOfMemoryError on large ResultSet

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John McCaskey wrote: | The problem is not the memory on the database server, but on the client | running the JDBC connection. Seems that when you retrieve the result it | is trying to store everything in memory at once. | | Here is some info from the

Re: Large resultset

-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

Large resultset

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 it a bug in setFetchSize? Does J/Connector ignore it? Have I totally

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 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

AW: Large resultset

Hi, why don't you try to solve the problem with ordinary sql-selects. You can take select . limit regards Reiner -Ursprüngliche Nachricht- Von: Roland Carlsson [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 11. März 2003 12:54 An: [EMAIL PROTECTED] Betreff: Large resultset

Re: Large resultset

] 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 still get the whole ResultSet at once and then I get an OutOfMemoryError

Re: Large resultset

it automatically gets the next portion. Thanks roland Carlsson - Original Message - From: Rusch (ext) Reiner [EMAIL PROTECTED] To: 'Roland Carlsson' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 12:59 PM Subject: AW: Large resultset Hi, why don't you try to solve the problem

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'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

Re: Large resultset

: [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'd somehow would like J/Connector to fetch only small pieces using