Exceptions used with SQLAlchemy.
The base exception class is SQLAlchemyError. Exceptions which are raised as a result of DBAPI exceptions are all subclasses of DBAPIError.
Bases: sqlalchemy.exc.SQLAlchemyError
Raised when an invalid or conflicting function argument is supplied.
This error generally corresponds to construction time state errors.
Bases: sqlalchemy.exc.SQLAlchemyError
Raised by topological sorts when a circular dependency is detected
Bases: sqlalchemy.exc.SQLAlchemyError
Raised when an error occurs during SQL compilation
Bases: sqlalchemy.exc.SQLAlchemyError
Raised when the execution of a database operation fails.
DBAPIError wraps exceptions raised by the DB-API underlying the database operation. Driver-specific implementations of the standard DB-API exception types are wrapped by matching sub-types of SQLAlchemy’s DBAPIError when possible. DB-API’s Error type maps to DBAPIError in SQLAlchemy, otherwise the names are identical. Note that there is no guarantee that different DB-API implementations will raise the same exception type for any given error condition.
If the error-raising operation occured in the execution of a SQL statement, that statement and its parameters will be available on the exception object in the statement and params attributes.
The wrapped exception object is available in the orig attribute. Its type and properties are DB-API implementation specific.
Bases: sqlalchemy.exc.DatabaseError
Wraps a DB-API DataError.
Bases: sqlalchemy.exc.DBAPIError
Wraps a DB-API DatabaseError.
Bases: sqlalchemy.exc.SQLAlchemyError
A disconnect is detected on a raw DB-API connection.
This error is raised and consumed internally by a connection pool. It can be raised by a PoolListener so that the host pool forces a disconnect.
Bases: sqlalchemy.exc.SQLAlchemyError
Raised when a schema name is beyond the max character limit
Bases: sqlalchemy.exc.DatabaseError
Wraps a DB-API IntegrityError.
Bases: sqlalchemy.exc.DBAPIError
Wraps a DB-API InterfaceError.
Bases: sqlalchemy.exc.DatabaseError
Wraps a DB-API InternalError.
Bases: sqlalchemy.exc.SQLAlchemyError
SQLAlchemy was asked to do something it can’t do.
This error generally corresponds to runtime state errors.
Bases: sqlalchemy.exc.InvalidRequestError
Raised by ForeignKey to indicate a reference cannot be resolved.
Bases: sqlalchemy.exc.NoReferenceError
Raised by ForeignKey when the referred Column cannot be located.
Bases: sqlalchemy.exc.NoReferenceError
Raised by ForeignKey when the referred Table cannot be located.
Bases: exceptions.KeyError, sqlalchemy.exc.InvalidRequestError
A nonexistent column is requested from a RowProxy.
Bases: sqlalchemy.exc.InvalidRequestError
Table does not exist or is not visible to a connection.
Bases: sqlalchemy.exc.DatabaseError
Wraps a DB-API NotSupportedError.
Bases: sqlalchemy.exc.DatabaseError
Wraps a DB-API OperationalError.
Bases: sqlalchemy.exc.DatabaseError
Wraps a DB-API ProgrammingError.
Bases: sqlalchemy.exc.InvalidRequestError
An operation was requested from a connection, cursor, or other object that’s in a closed state.
Bases: exceptions.DeprecationWarning
Issued once per usage of a deprecated API.
Bases: exceptions.PendingDeprecationWarning
Issued once per usage of a deprecated API.
Bases: exceptions.RuntimeWarning
Issued at runtime.
Bases: exceptions.Exception
Generic error class.
alias of DBAPIError
Bases: sqlalchemy.exc.SQLAlchemyError
Raised when a connection pool times out on getting a connection.
Bases: sqlalchemy.exc.InvalidRequestError
SQL was attempted without a database connection to execute it on.