Well, there's the transaction manager middleware that handles database errors right now.
If it's handling of errors isn't what you want, you can change it out for something more specific to your needs. We're using repoze.tm2 in tg2 and it's configured into the middleware stack by the AppConfig object. Seems like tm2 does pretty much what you want except that the way we've configured it it catches all transaction errors, and also rolls back on any other python errors, or HTTP error status codes. On Mon, Dec 1, 2008 at 7:53 PM, Brian <[EMAIL PROTECTED]> wrote: > > I want to be able to catch database transaction errors, roll the > transaction back, and re-direct the user to a page. (That page may > depend on the page from which the error occurred, but that's a lesser > need.) Would somebody please tell me a uniform way to do this (without > try...catching every SQL statement) in TG 2.0 (1.9.7b1)? I prefer a > solution that handles this error at a single point, without wrapping > every method with a handler, if one exists. > > Thanks, > Brian > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
