Hey folks, pyramid_tm 2.0 has been released. This is a semi-major change to the library which manages your transactions.
The major change is that the commit (or abort) now occurs OVER the exception view which means the transaction is still open during exception views. This means that: 1) You can now touch managed objects and perform database queries inside of exception views and they will affect the active transaction. 2) Any changes done in an exception view will be aborted unless done in a database session that is not joined to the request.tm transaction manager. 2) Any exceptions that occur due to commit failures will not be caught by default. This situation may improve in the future either within pyramid_tm itself or via pyramid_retry in the upcoming pyramid 1.9 release. For some more information about how this may affect your application please check out this previous post to the mailing list: https://groups.google.com/d/msg/pylons-discuss/OOh5Hn0EWz8/ODkl5OXMAQAJ The release documentation is available at http://docs.pylonsproject.org/projects/pyramid-tm/en/latest/ . Thanks! - Pyramid core developers -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAKdhhwG1XLOO1p3Kag%2B2%3Dy5rCOeg%3DFRwS4y3tw3GJV8G5Pu8DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
