By default, TurboGears wraps exposed controller methods in a transaction that gets committed after the controller has run. This commit can generate exceptions (most notably when the condition of mapped objects violates an integrity constraint in the database). How can I catch/handle these exceptions without turning off the automatic transaction handling?
I have looked into using the exception_handler decorator (which might not even work in this situation; I'm not sure) but that would disallow access to the controller arguments. The specific case that I am working with is an entity creation with a duplicate name in a unique column. I want to be able to catch the exception, flash and error message, and re-display the entry form still filled in from their previous input. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
