7b24e458c7
- move all the comments that got shoved below the fixture grabs back up
2011-03-27 17:19:00 -04:00
68a350d462
- remove test.sql._base, test.engine._base, test.orm._base, move those classes to a new test.lib.fixtures module
...
- move testing.TestBase to test.lib.fixtures
- massive search and replace
2011-03-27 16:27:27 -04:00
fde2a7f8fe
Informix and postgresql reserved words changes -- almost done.
2011-03-15 16:56:45 -04:00
33eae4a140
make it more explicit in tests which dialect we want to use for things
2011-02-11 11:24:54 -05:00
350aed3fdb
- whitespace removal bonanza
2011-01-02 14:23:42 -05:00
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
e1402efb19
- move sqlalchemy.test to test.lib
2010-11-15 19:37:50 -05:00
87c50f2aac
Because of changes to SQLAlchemy bind parameter placement, removed all mxodbc test disabling statements having this pattern: @testing.crashes('mssql+mxodbc', """Invalid bind parameter placement:
2010-03-17 16:27:39 -06:00
d6b5550f42
Disabling tests for mssql+mxodbc where mxODBC cursor.execute chokes on invalid placement of bind parameter "?" within the SQL statement.
2010-03-16 16:57:54 -06:00
c5e29f0eed
fixed the illegal_initial_chars collection + unit test, [ticket:1659]
2010-01-21 15:56:23 +00:00
8fc5005dfe
merge 0.6 series to trunk.
2009-08-06 21:11:27 +00:00
45cec095b4
- unit tests have been migrated from unittest to nose.
...
See README.unittests for information on how to run
the tests. [ticket:970]
2009-06-10 21:18:24 +00:00
Mike Bayer