delta/python-packages/sqlalchemy.git/test/engine/test_reconnect.py, branch pr/156

- simplify the "noconnection" error handling, setting

2014-12-08T19:05:20+00:00

_handle_dbapi_exception_noconnection() to only invoke in the case
of raw_connection() in the constructor of Connection.   in all other
cases the Connection proceeds with _handle_dbapi_exception() including
revalidate.

- adjust _revalidate_connection() again such that we pass a _wrap=False

2014-12-06T00:08:47+00:00

to it, so that we say we will do the wrapping just once right here
in _execute_context() / _execute_default().  An adjustment is made
to _handle_dbapi_error() to not assume self.__connection in case
we are already in an invalidated state

further adjustment to
0639c199a547343d62134d2f233225fd2862ec45, 41e7253dee168b8c26c49, #3266

- Fixed bug where a "branched" connection, that is the kind you get

2014-09-26T20:25:26+00:00

when you call :meth:`.Connection.connect`, would not share transaction
status with the parent.  The architecture of branching has been tweaked
a bit so that the branched connection defers to the parent for
all transactional status and operations.
fixes #3190

- Fixed bug where a "branched" connection, that is the kind you get

2014-09-26T18:55:36+00:00

when you call :meth:`.Connection.connect`, would not share invalidation
status with the parent.  The architecture of branching has been tweaked
a bit so that the branched connection defers to the parent for
all invalidation status and operations.
fixes #3215

PEP8 tidy of test/engine/test_reconnect

2014-08-02T14:29:36+00:00

- more pg8000 tests passing

2014-07-25T20:39:44+00:00

- vastly improve the "safe close cursor" tests in test_reconnect

2014-05-30T20:24:38+00:00

- Fixed bug which would occur if a DBAPI exception
occurs when the engine first connects and does its initial checks,
and the exception is not a disconnect exception, yet the cursor
raises an error when we try to close it.  In this case the real
exception would be quashed as we tried to log the cursor close
exception via the connection pool and failed, as we were trying
to access the pool's logger in a way that is inappropriate
in this very specific scenario. fixes #3063

Fix many typos throughout the codebase

2014-04-26T20:13:13+00:00

Found using: https://github.com/intgr/topy

- fix the uuid routine here to not run out of uuids

2014-03-24T15:57:38+00:00

- A major improvement made to the mechanics by which the :class:`.Engine`

2014-03-22T22:45:39+00:00

recycles the connection pool when a "disconnect" condition is detected;
instead of discarding the pool and explicitly closing out connections,
the pool is retained and a "generational" timestamp is updated to
reflect the current time, thereby causing all existing connections
to be recycled when they are next checked out.   This greatly simplifies
the recycle process, removes the need for "waking up" connect attempts
waiting on the old pool and eliminates the race condition that many
immediately-discarded "pool" objects could be created during the
recycle operation. fixes #2985