Thrown from the C++ to SQL data type conversion routine when it can't figure out how to map the type. More...
#include <exceptions.h>
Inheritance diagram for mysqlpp::TypeLookupFailed:
Collaboration diagram for mysqlpp::TypeLookupFailed:
Public Member Functions | |
| TypeLookupFailed (const std::string &w) | |
| Create exception object. | |
 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 | |
Detailed Description
Thrown from the C++ to SQL data type conversion routine when it can't figure out how to map the type.
This exception is not optional. The only alternatives when this happens are equally drastic: basically, either iterate past the end of an array (crashing the program) or call assert() to crash the program nicely. At least this way you have some control over how your program ends. You can even ignore the error and keep on going: this typically happens when building a SQL query, so you can handle it just the same as if the subsequent query execution failed.
The documentation for this class was generated from the following file:
