Bug #15321 Statement.setFetchSize() not work
Submitted: 29 Nov 2005 17:43 Modified: 31 Mar 2014 10:29
Reporter: Mauricio Kanada Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:3.0.14 OS:Windows (Windows (relevant?))
Assigned to: Alexander Soklakov CPU Architecture:Any

[29 Nov 2005 17:43] Mauricio Kanada
Description:
I'm readin a huge table using 'select * from <table>'. Before 'stmt.executeQuery()' I perform 'stmt.setFecthSize(100)', but this seems not work, and I get a 'OutOfMemoryError' in 'stmt.executeQuery()'.

My tiny program has only this query, and so, I can only use the memory setting for JVM.

How to repeat:
In my case, I created a query 'select * from <table>' without any 'where' clause and one table with 1.4 million rows.

Suggested fix:
Respect de hint specified by the method 'setFetchSize()' in interfaces 'Statement' and 'ResultSet'.
[30 Nov 2005 22:11] Vasily Kishkin
I need some test case to understand what was happend there. Could you please write here table definition and some test case ?
[1 Jan 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[31 Mar 2014 10:29] Alexander Soklakov
I close this report as "Can't repeat" because there is no feedback for a long time and codebase is too old. Please, feel free to reopen it if the problem still exists in current driver.