Jonathan, You probably want transaction.savepoint() in that case. There's a pretty extensive discussion here showing savepoints (and rollbacks to savepoints) as a way of creating sub-transactions with pyramid_tm:
https://groups.google.com/d/msg/pylons-discuss/5Mj4R3YMXhI/GVFj2Du33JAJ You can of course do all of that in SQLAlchemy without pyramid_tm doing it for you, so if the savepoints don't cover your use cases that's something to consider. -Eric On Tue, Feb 14, 2012 at 2:24 PM, Jonathan Vanasco <jonat...@findmeon.com>wrote: > eric- > > thanks. I'll post a followup on the pylons list. > > i've already got a call to session.flush() > > the problem is that i need the transaction itself committed in this > block. i have a series of "database transactions" that happen within > the request. the first "database transaction" should error out on a > fail and it's very important to save that information for perpetuity. > subsequent "database transactions" could fail , and are just hidden. > > it sounds like the design of pyramid_tm is one transaction per > request, which is really weird. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalchemy@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
