slower each time you run the tests. This seems to be related to the constant
creation/dropping of tables. Running a "VACUUM FULL" on the database will
speed it up again.
+
+MSSQL: Tests that involve multiple connections require Snapshot Isolation
+ability implented on the test database in order to prevent deadlocks that will
+occur with record locking isolation. This feature is only available with
+MSSQL 2005 and greater. For example::
+
+ ALTER DATABASE MyDatabase
+ SET ALLOW_SNAPSHOT_ISOLATION ON
+
+ ALTER DATABASE MyDatabase
+ SET READ_COMMITTED_SNAPSHOT ON
assert len(session.query(User).filter_by(name='Johnny').all()) == 0
session.close()
- @testing.crashes('mssql', 'test causes mssql to hang')
@testing.requires.independent_connections
@engines.close_open_connections
@testing.resolve_artifact_names
assert testing.db.connect().execute("select count(1) from users").scalar() == 1
sess.close()
- @testing.crashes('mssql', 'test causes mssql to hang')
@testing.requires.independent_connections
@engines.close_open_connections
@testing.resolve_artifact_names
eq_(q.one(), Address(email_address='foo'))
- @testing.crashes('mssql', 'test causes mssql to hang')
@testing.requires.independent_connections
@engines.close_open_connections
@testing.resolve_artifact_names
session.commit()
assert session.connection().execute("select count(1) from users").scalar() == 2
- @testing.crashes('mssql', 'test causes mssql to hang')
@testing.fails_on('sqlite', 'FIXME: unknown')
@testing.resolve_artifact_names
def test_transactions_isolated(self):