- Firebird now uses dialect.preparer to format sequences names
-- Fixed breakage with postgres and multiple two phase transactions. For some
- reason the implicitly started transaction is not enough. [ticket:810]
+- Fixed breakage with postgres and multiple two-phase transactions. Two-phase
+ commits and and rollbacks didn't automatically end up with a new transaction
+ as the usual dbapi commits/rollbacks do. [ticket:810]
- Added an option to the _ScopedExt mapper extension to not automatically
save new objects to session on object initialization.
return sqltypes.adapt_type(typeobj, colspecs)
def do_begin_twophase(self, connection, xid):
- # Two phase transactions seem to require that the transaction is explicitly started.
- # The implicit transactions that usually work aren't enough.
- connection.execute(sql.text("BEGIN"))
self.do_begin(connection.connection)
def do_prepare_twophase(self, connection, xid):
# Must find out a way how to make the dbapi not open a transaction.
connection.execute(sql.text("ROLLBACK"))
connection.execute(sql.text("ROLLBACK PREPARED %(tid)s", bindparams=[sql.bindparam('tid', xid)]))
+ connection.execute(sql.text("BEGIN"))
else:
self.do_rollback(connection.connection)
if recover:
connection.execute(sql.text("ROLLBACK"))
connection.execute(sql.text("COMMIT PREPARED %(tid)s", bindparams=[sql.bindparam('tid', xid)]))
+ connection.execute(sql.text("BEGIN"))
else:
self.do_commit(connection.connection)