one of my apps uses pyramid_tm, but has reached a point where one (possibly > two) views (out of dozens) need to make explicit commits with the > SqlAlchemy session. >
Because this does not fit well in the view/request model, I would usually try to offload these tasks to a worker processes (Celery) where it is much easier to have a explicit control over the transaction cycle. A request would only serve as a trigger for the background process. It does not work for all kind of use cases, though. -Mikko -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAK8RCUv3X0WNkKENzAH-nt7_tR34KLTeJde-jcfOs9r35xRyfw%40mail.gmail.com.
