ZopeTransaction just manages the transactions. pyramid_tm tells transaction to commit on non-errors ; rollback on errors.
You're not using that in Production as well, are you? That sounds more like an anti-pattern than the right way to do things. On Tuesday, August 20, 2013 4:58:00 PM UTC-4, James Carroll wrote: > > I've got a pretty sophisticated server going... > it's using unit tests that will PUT some data, then do a GET to verify, > then rollback the transaction to restore the database to its original state. > Doing one session per request kills that, since the new session doesn't > have the dynamic state of the first one. > > The ZopeTransactionManager really should be solving this if I understand > correctly.... > >> >> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
