delta/python-packages/sqlalchemy.git/lib/sqlalchemy/exc.py, branch pr/259

- happy new year

2016-01-29T16:25:37+00:00

(cherry picked from commit 859379e2fcc4506d036700ba1eca4c0ae526a8ee)

- Added support for the case of the misbehaving DBAPI that has

2015-05-15T16:38:28+00:00

pep-249 exception names linked to exception classes of an entirely
different name, preventing SQLAlchemy's own exception wrapping from
wrapping the error appropriately.
The SQLAlchemy dialect in use needs to implement a new
accessor :attr:`.DefaultDialect.dbapi_exception_translation_map`
to support this feature; this is implemented now for the py-postgresql
dialect.
fixes #3421

- tweaks regarding the use_alter update

2015-03-13T20:22:01+00:00

- copyright 2015

2015-03-10T19:24:28+00:00

- remove the "edges" from the message here. It's illegible

2015-01-01T18:14:05+00:00

- Exception messages have been spiffed up a bit. The SQL statement

2014-10-17T23:37:45+00:00

and parameters are not displayed if None, reducing confusion for
error messages that weren't related to a statement.  The full
module and classname for the DBAPI-level exception is displayed,
making it clear that this is a wrapped DBAPI exception.  The
statement and parameters themselves are bounded within a bracketed
sections to better isolate them from the error message and from
each other.
fixes #3172

- the test_except test was doing an unnecessary workaround of some kind,

2014-10-12T23:37:14+00:00

take that out, restore the better exception logic in exc

- roll back part of pr 140 to get exception wrapping working again

2014-10-12T13:54:44+00:00

cleanup exception handling - use new exception hierarchy (since python 2.5)

2014-10-02T20:00:31+00:00

- The exception wrapping system for DBAPI errors can now accommodate

2014-07-29T18:06:43+00:00

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