]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- parent transactions weren't started on the connection when adding a connection...
authorAnts Aasma <ants.aasma@gmail.com>
Sun, 20 Jan 2008 03:22:00 +0000 (03:22 +0000)
committerAnts Aasma <ants.aasma@gmail.com>
Sun, 20 Jan 2008 03:22:00 +0000 (03:22 +0000)
commit9f366afdda4b508eb4ef3e626da2fec98ad04773
tree62aeb76e50e813fde97134e830b2a0de39e06dc4
parent4be99db15b7a62b37493c86da07bcc787f44a7df
- 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.
CHANGES
doc/build/content/session.txt
lib/sqlalchemy/ext/activemapper.py
lib/sqlalchemy/orm/session.py
test/orm/session.py