Mike Bayer f458ef8456 - these tests don't test anything in SQLAlchemy - from our perpsective, ...

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.

2014-09-19 12:41:07 -04:00

..

__init__.py

reorganized unit tests into subdirectories

2006-06-05 17:25:51 +00:00

test_bind.py

- A large refactoring of the `sqlalchemy.sql` package has reorganized

2013-08-12 17:50:37 -04:00

test_ddlevents.py

- more pg8000 tests passing

2014-07-25 16:39:44 -04:00

test_execute.py

- Fixed bug that affected generally the same classes of event

2014-09-18 17:49:07 -04:00

test_logging.py

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

2014-08-20 12:01:20 -04:00

test_parseconnect.py

- The :func:.engine_from_config function has been improved so that

2013-12-07 18:38:15 -05:00

test_pool.py

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

2014-08-07 12:36:50 -04:00

test_processors.py

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

test_reconnect.py

PEP8 tidy of test/engine/test_reconnect

2014-08-02 15:29:36 +01:00

test_reflection.py

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

2014-09-02 14:18:09 -04:00

test_transaction.py

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

2014-09-19 12:41:07 -04:00