Just wondering in what scenarios, one would use the transaction management package, pyramid_tm. I understand transactions as related to databases, but I can not think of the other intended situations where I should use this.
In the pyramid_email transaction, it gives an example of rolling back a transaction when there is an error in the view caused by a database: "Wrapping email sending in the transaction manager. If you have a view that sends a customer an email for example, and there is an error in that view (for example, a database error) then this ensures that the email is not sent." Are there any other scenarios that I should watch out for? -- 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.
