From 9f366afdda4b508eb4ef3e626da2fec98ad04773 Mon Sep 17 00:00:00 2001 From: Ants Aasma Date: Sun, 20 Jan 2008 03:22:00 +0000 Subject: - parent transactions weren't started on the connection when adding a connection to a nested session transaction. - session.transaction now always refers to the innermost active transaction, even when commit/rollback are called directly on the session transaction object. - when preparing a two-phase transaction fails on one connection all the connections are rolled back. - two phase transactions can now be prepared. - session.close() didn't close all transactions when nested transactions were used. - rollback() previously erroneously set the current transaction directly to the parent of the transaction that could be rolled back to. - autoflush for commit() wasn't flushing for simple subtransactions. --- lib/sqlalchemy/ext/activemapper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/sqlalchemy/ext') diff --git a/lib/sqlalchemy/ext/activemapper.py b/lib/sqlalchemy/ext/activemapper.py index b28ada0af..02f4b5b35 100644 --- a/lib/sqlalchemy/ext/activemapper.py +++ b/lib/sqlalchemy/ext/activemapper.py @@ -13,7 +13,7 @@ import sys # metadata = ThreadLocalMetaData() Objectstore = scoped_session -objectstore = scoped_session(sessionmaker(autoflush=True)) +objectstore = scoped_session(sessionmaker(autoflush=True, transactional=False)) # # declarative column declaration - this is so that we can infer the colname -- cgit v1.2.1