Bug #2612 | ResultSet fetchSize default is not working | ||
---|---|---|---|
Submitted: | 2 Feb 2004 8:17 | Modified: | 2 Feb 2004 8:35 |
Reporter: | Daniel Taut | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 3.0.10 stable | OS: | Linux (Linux) |
Assigned to: | Mark Matthews | CPU Architecture: | Any |
[2 Feb 2004 8:17]
Daniel Taut
[2 Feb 2004 8:35]
Mark Matthews
Statement.setFetchSize() is a no-op in MySQL (because there are no cursors in MySQL), and thus the same thing is applicable to ResultSet.setFetchSize() and ResultSet.getFetchSize(). The spec states that setFetchSize() is a _hint_, and that getFetchSize() should return the actual fetch size _in_use_. Since setFetchSize() doesn't actually affect the 'in-use' value, it would be improper to return the value passed in the statement to setFetchSize() via ResultSet.getFetchSize(). In fact, really, the driver does have a bug, in that it currently _does_ return the fetch size for a given interface (in preparation for cursors being added to MySQL).