[EMAIL PROTECTED] writes: > On Nov 30, 2005, at 6:52 AM, Kevin Dangoor wrote: > > > A nice workaround, I think, will be to implicitly start a Transaction > > for each request, which is something we've talked about before: > > http://trac.turbogears.org/turbogears/ticket/80 > > Just a thought that it would be very useful to do this and have exception > handling to roll back a transaction if the application throws an exception.
I'm more worried about how to give feedback to user. If anything goes wrong -- such as I raised an exception at DB-level -- I want the user to see some error message or indication that what he did didn't work. Today I grab the exception error message and pass it to tg_flash or create a custom message based on the exception raised (e.g. I can have either "ProgrammingError" or "IntegrityError" in some places). Nesting transactions is something that is OK with PostgreSQL 8+, but how's it for other SQLObject supported RDBMSs? Be seeing you, -- Jorge Godoy <[EMAIL PROTECTED]>
