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

Allow metadata.reflect() to recover from unreflectable tables

2017-05-22T19:51:07+00:00

Added support for views that are unreflectable due to stale
table definitions, when calling :meth:`.MetaData.reflect`; a warning
is emitted for the table that cannot respond to ``DESCRIBE``
but the operation succeeds.  The MySQL dialect now
raises UnreflectableTableError which is in turn caught by
MetaData.reflect().  Reflecting the view standalone raises
this error directly.

Change-Id: Id8005219d8e073c154cc84a873df911b4a6cf4d6
Fixes: #3871

Integrate "pre-ping" into connection pool.

2017-03-20T22:01:23+00:00

Added native "pessimistic disconnection" handling to the :class:`.Pool`
object.  The new parameter :paramref:`.Pool.pre_ping`, available from
the engine as :paramref:`.create_engine.pool_pre_ping`, applies an
efficient form of the "pre-ping" recipe featured in the pooling
documentation, which upon each connection check out, emits a simple
statement, typically "SELECT 1", to test the connection for liveness.
If the existing connection is no longer able to respond to commands,
the connection is transparently recycled, and all other connections
made prior to the current timestamp are invalidated.

Change-Id: I89700d0075e60abd2250e54b9bd14daf03c71c00
Fixes: #3919

update for 2017 copyright

2017-01-04T17:39:24+00:00

Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de

Check for supports_execution at ClauseElement base

2016-08-31T21:04:35+00:00

Raise a more descriptive exception / message when ClauseElement
or non-SQLAlchemy objects that are not "executable" are erroneously
passed to ``.execute()``; a new exception ObjectNotExecutableError
is raised consistently in all cases.

Change-Id: I2dd393121e2c7e5b6b9e40286a2f25670876e8e4
Fixes: #3786

- happy new year

2016-01-29T16:20:22+00:00

- 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

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