sqlalchemy

mirror of https://github.com/sqlalchemy/sqlalchemy.git synced 2026-05-30 04:24:38 -04:00

Files

T

Mike Bayer 8e24584d8d - ResultProxy and friends always reference the DBAPI connection at the same time

as the cursor.  There is no reason for CursorFairy - the only use case would be,
end-user is using the pool or pool.manage with DBAPI connections, uses a cursor,
deferences the owning connection and continues using cursor.  This is an almost
nonexistent use case and isn't correct usage at a DBAPI level.  Take out CursorFairy.
- move the "check for a dot in the colname" logic out to the sqlite dialect.

2010-12-05 00:46:11 -05:00

__init__.py

reorganized unit tests into subdirectories

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

_base.py

- unit tests have been migrated from unittest to nose.

2009-06-10 21:18:24 +00:00

test_case_statement.py

- move sqlalchemy.test to test.lib

2010-11-15 19:37:50 -05:00

test_compiler.py

- sqlalchemy.test and nose plugin moves back to being entirely