Installation guide

10. mxODBC Exceptions and Error Handling
Error is a subclass of exceptions.StandardError.
Warning
Exception raised for important warnings like data truncations while inserting,
etc.
Warning is a subclass of
exceptions.StandardError. This may change in a
future release to some other baseclass indicating warnings.
InterfaceError
Exception raised for errors that are related to the interface rather than the
database itself.
DatabaseError
Exception raised for errors that are related to the database.
DataError
Exception raised for errors that are due to problems with the processed data
like division by zero, numeric out of range, etc.
OperationalError
Exception raised for errors that are related to the database's operation and not
necessarily under the control of the programmer, e.g. an unexpected
disconnect occurs, the data source name is not found, a transaction could not
be processed, a memory allocation error occurred during processing, etc.
IntegrityError
Exception raised when the relational integrity of the database is affected, e.g. a
foreign key check fails.
InternalError
Exception raised when the database encounters an internal error, e.g. the
cursor is not valid anymore, the transaction is out of sync, etc.
ProgrammingError
Exception raised for programming errors, e.g. table not found or already exists,
syntax error in the SQL statement, wrong number of parameters specified,
performing operations on closed connections etc.
NotSupportedError
Exception raised in case a method or database API was used which is not
supported by the database, e.g. requesting a .rollback() on a connection that
does not support transaction or has transactions turned off.
This is the exception inheritance layout:
StandardError
|__Warning
|__Error
|__InterfaceError
|__DatabaseError
|__DataError
159