delta/python-packages/sqlalchemy.git/test/engine, branch pr/139

- these tests don't test anything in SQLAlchemy - from our perpsective,

2014-09-19T16:41:07+00:00

we need to be in transactions (tested elsewhere) and we need to
emit the correct FOR UPDATE strings (tested elsewhere).  There's nothing
in SQLA to be tested as far as validating that for update causes exceptions
or not, and these tests frequently fail as they are timing sensitive.

- Fixed bug that affected generally the same classes of event

2014-09-18T21:49:07+00:00

as that of :ticket:`3199`, when the ``named=True`` parameter
would be used.  Some events would fail to register, and others
would not invoke the event arguments correctly, generally in the
case of when an event was "wrapped" for adaption in some other way.
The "named" mechanics have been rearranged to not interfere with
the argument signature expected by internal wrapper functions.
fixes #3197

- An adjustment to table/index reflection such that if an index

2014-09-02T18:18:09+00:00

reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180

- Fixed bug in connection pool logging where the "connection checked out"

2014-08-20T16:01:20+00:00

debug logging message would not emit if the logging were set up using
``logging.setLevel()``, rather than using the ``echo_pool`` flag.
Tests to assert this logging have been added.  This is a
regression that was introduced in 0.9.0.
fixes #3168

- pep8 cleanup

2014-08-20T13:08:59+00:00

Merge remote-tracking branch 'origin/pr/125' into pr125

2014-08-16T17:48:57+00:00

- The string keys that are used to determine the columns impacted

2014-08-15T00:00:35+00:00

for an INSERT or UPDATE are now sorted when they contribute towards
the "compiled cache" cache key.   These keys were previously not
deterministically ordered, meaning the same statement could be
cached multiple times on equivalent keys, costing both in terms of
memory as well as performance.
fixes #3165

Providing an autoload_with info automatically sets autoload to True

2014-08-09T19:43:32+00:00

- take out the iterator approach here as it does not support concurrent access

2014-08-07T16:36:50+00:00

two_phase_recover, COMMIT PREPARED in transaction

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

In test/engine/test_transaction/test_two_phase_recover(), a COMMIT
PREPARED is issued while in a transaction. This causes an error, and
a prepared transaction is left hanging around which causes
the subsequent test to hang. I've altered the test to execute the
offending query with autocommit=true, then when it gets to the COMMIT
PRPARED it can go ahead.

There's another complication for pg8000 because its tpc_recover() method
started a transaction if one wasn't already in progress. I've decided
that this is incorrect behaviour and so from pg8000-1.9.13 this method
never starts or stops a transaction.