I did indeed mean transaction.commit(). I'm happy to know that the transaction will be committed on it's own if I don't do it, I think I will take advantage of that.
I'm also curious about this mortar_rdb thing... But other than that bit of trivia, any reasons I should structure my code differently? Thanks! On May 20, 8:26 am, Chris Withers <[email protected]> wrote: > On 20/05/2011 09:35, Chris McDonough wrote: > > > On Fri, 2011-05-20 at 00:43 -0700, Gopalakrishnan S wrote: > >> Does transaction manager commit sqlalchemy session? Really? > >> I like the idea still.. > > > Yes, at least if you have ZopeTransactionExtension configured in your > > session. > > ...which mortar_rdb does for you: > > http://packages.python.org/mortar_rdb/use.html > > You don't have to use mortar_rdb's declarative_base or controlled stuff > to use registerSession and getSession ;-) > > </plug> > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > -http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
