Bug #8792 supportsResultSetConcurrency incorrectly returning false
| Submitted: | 24 Feb 2005 20:34 | Modified: | 17 Mar 2005 22:47 |
|---|---|---|---|
| Reporter: | Jeremiah Johnson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / J | Severity: | S3 (Non-critical) |
| Version: | 3.1.7 | OS: | Linux (Linux) |
| Assigned to: | Mark Matthews | CPU Architecture: | Any |
[17 Mar 2005 22:47]
Mark Matthews
Fixed for 3.1.8. Thanks for the bug report. A nightly snapshot with this fix will be available after 00:00 GMT Mar-18-2005 at http://downloads.mysql.com/snapshots.php.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: A call to supportsResultSetConcurrency with TYPE_FORWARD_ONLY and CONCUR_READ_ONLY returns a false. I believe that this should return true. How to repeat: Connection con = DriverManager.getConnection("jdbc:mysql:///test", "test", "test"); if (!con.getMetaData().supportsResultSetConcurrency(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY)) { // fail } Statement stmt = con.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY); I would like to get to the statement in this case, but supportsResultSetConcurrency returns false and fails my method. Suggested fix: Change supportsResultSetConcurrency to return true when the parameters are TYPE_FORWARD_ONLY and CONCUR_READ_ONLY.