Bug #69031 | Connection losses are not detected by queries with "forward-only" result sets | ||
---|---|---|---|
Submitted: | 22 Apr 2013 12:58 | Modified: | 27 Oct 2014 17:08 |
Reporter: | Dario Andreani | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / C++ | Severity: | S3 (Non-critical) |
Version: | 1.1.3 | OS: | Windows |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[22 Apr 2013 12:58]
Dario Andreani
[13 Jun 2013 12:31]
Lawrenty Novitsky
Thank you Dario for your report. I can see the problem here.
[28 Aug 2013 11:06]
Bhalchandra Gokhale
I encountered upon the same bug with JDBC API on Windows7 64-bit machine (both client and server) Versions: Database version 5.1.68 Driver version 5.1.26
[20 Oct 2014 13:07]
Hemant Dangi
Posted by developer: Committed in rev#984. Added checks in MySQL_ResultSet::next() and MySQL_Prepared_ResultSet::next() to throw exception when connection is lost.
[27 Oct 2014 17:08]
Paul DuBois
Noted in 1.1.5 changelog. With the result set type set to TYPE_FORWARD_ONLY, Statement::executeQuery() returns almost immediately, but MySQL_ResultSet::next() and MySQL_Prepared_ResultSet::next() returned false if the connection was lost rather than throwing an exception, making it impossible to distinguish loss of connection from normal end of the result set. MySQL_ResultSet::next() and MySQL_Prepared_ResultSet::next() now throw an exception when the connection is lost.