Bug #25517 Stetement.setMaxRows becomes useless when using cursor fetch
Submitted: 10 Jan 2007 3:31 Modified: 13 Apr 2007 8:36
Reporter: Yuan WANG Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:5.0.4 OS:Any
Assigned to: CPU Architecture:Any

[10 Jan 2007 3:31] Yuan WANG 
Description:
If we set useCursorFetch=true in the connection url and setFetchSize for a Statement, then Stetement.setMaxRows becomes useless, the server will always return all records.

How to repeat:
As in description
[15 Jan 2007 13:08] Tonci Grgin 
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Hi and thanks for your report. Can you please provide:
  - MySQL server version
  - Host OS and version (if relevant)
  - JRE version
  - Small but *complete* test case exhibiting this behavior
[15 Jan 2007 17:36] Tonci Grgin 
Verified as described by reporter.
[22 Mar 2007 20:58] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/22704
[13 Apr 2007 8:36] MC Brown 
A note has been added to the 5.0.6 changelog.