On 30 Nov 2005 19:04:28 -0200, Jorge Godoy <[EMAIL PROTECTED]> wrote: > 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).
I'm thinking that expose will catch the exception, do a rollback and then raise it again. (If any exceptions occur during the commit, those will be raised). So, you can still define a _cpOnError method to display a proper message to the user. > Nesting transactions is something that is OK with PostgreSQL 8+, but how's it > for other SQLObject supported RDBMSs? Currently, the code doesn't really give you a chance to nest transactions. I do realize there are some cases where you might want to do that... it's worth opening a ticket on. As of right this moment, though. the connection hub doesn't nest transactions. Kevin
