MySQL++
3.3.0
|
Exception thrown when there is a problem related to the database server connection. More...
#include <exceptions.h>
Public Member Functions | |
ConnectionFailed (const char *w="", int e=0) | |
Create exception object. More... | |
int | errnum () const |
Return the error number corresponding to the error message returned by what(), if any. More... | |
Public Member Functions inherited from mysqlpp::Exception | |
Exception (const Exception &e) MAY_THROW() | |
Create exception object as copy of another. | |
Exception & | operator= (const Exception &rhs) throw () |
Assign another exception object's contents to this one. | |
~Exception () throw () | |
Destroy exception object. | |
virtual const char * | what () const throw () |
Returns explanation of why exception was thrown. | |
Additional Inherited Members | |
Protected Member Functions inherited from mysqlpp::Exception | |
Exception (const char *w="") throw () | |
Create exception object. | |
Exception (const std::string &w) throw () | |
Create exception object. | |
Protected Attributes inherited from mysqlpp::Exception | |
std::string | what_ |
explanation of why exception was thrown | |
Exception thrown when there is a problem related to the database server connection.
This is thrown not just on making the connection, but also on shutdown and when calling certain of Connection's methods that require a connection when there isn't one.
|
inlineexplicit |
Create exception object.
w | explanation for why the exception was thrown |
e | the error number from the underlying database API |
|
inline |
Return the error number corresponding to the error message returned by what(), if any.
If the error number is 0, it means that the error message doesn't come from the underlying database API, but rather from MySQL++ itself. This happens when an error condition is detected up at this higher level instead of letting the underlying database API do it.