- changed milestone to 0.9.7
support non-standard DBAPI exception classes
Issue #3075
resolved
apparently psycopg2 has an OperationalError subclass psycopg2.extensions.TransactionRollbackError. We should be reporting this at least as an OperationalError and not dropping down to DBAPIError.
Comments (7)
-
reporter
-
reporter
- marked as major
-
reporter
- changed milestone to 0.9.8
-
reporter
- changed milestone to 0.9.7
-
reporter
- changed milestone to 0.9.8
-
reporter
- changed status to resolved
- The exception wrapping system for DBAPI errors can now accommodate
non-standard DBAPI exceptions, such as the psycopg2
TransactionRollbackError. These exceptions will now be raised
using the closest available subclass in
sqlalchemy.exc, in the case of TransactionRollbackError,sqlalchemy.exc.OperationalError. fixes#3075
→ <<cset 83326bf44c59>>
-
reporter
- The exception wrapping system for DBAPI errors can now accommodate
non-standard DBAPI exceptions, such as the psycopg2
TransactionRollbackError. These exceptions will now be raised
using the closest available subclass in
sqlalchemy.exc, in the case of TransactionRollbackError,sqlalchemy.exc.OperationalError. fixes#3075
→ <<cset 8513fb588f7f>>
- The exception wrapping system for DBAPI errors can now accommodate
non-standard DBAPI exceptions, such as the psycopg2
TransactionRollbackError. These exceptions will now be raised
using the closest available subclass in
- Log in to comment
