I'm using symfony with the default ORM: Propel 1.2 I don't want any web requests which result in any kind of un-handled exception to commit changes to the database. So I would like to:
* begin a transaction early in request processing * rollback the transaction if the request results in any kind of un- handled exception * commit the transaction late in request processing Currently, I think the best design for implementing this feature is as a symfony filter. The filter would begin a transaction before executing the next filter in the chain. It would catch any un-handled exceptions and rollback the transaction. Otherwise it would commit the transaction before returning. I don't know if this is the best design, or if there are negative issues associated. Has anyone else done something similar? Does anyone have opinions on implementing this behavior? Thanks and best wishes, Jack --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
