Rollback on Error

From: "Michael Paesold" <mpaesold(at)gmx(dot)at>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Rollback on Error
Date: 2004-09-14 09:39:32
Message-ID: 000901c49a3e$bd56f8e0$ad01a8c0@zaphod
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

I just read this in the MySQL manual:
(http://dev.mysql.com/doc/mysql/en/InnoDB_Error_handling.html)

"Error handling in InnoDB is not always the same as specified in the SQL
standard. According to the standard, any error during an SQL statement
should cause the rollback of that statement. InnoDB sometimes rolls back
only part of the statement, or the whole transaction. The following items
describe how InnoDB performs error handling:"

Ignore InnoDB, but read "According to the standard, any error during an SQL
statement should cause the rollback of that statement"...

I though the postgres behaviour of rolling back the whole transaction was
standard? If that is not the case, I don't understand why core seems to be
against a mode (GUC), where an implicit savepoint is generated before each
statement so that "rollback of the last statement" would be possible.

Is MySQL wrong on the standard, or has postgresql core attitude changed to
support the standard where possible - at least if the user wants?

Best Regards,
Michael Paesold

P.S: again thanks for PostgreSQL!

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Penhey 2004-09-14 09:49:43 plpgsql - raising exceptions with open cursors
Previous Message Gaetano Mendola 2004-09-14 08:52:04 Re: postgresql hanging (blocking) with smp kernel

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2004-09-14 09:53:16 Re: Rollback on Error
Previous Message Daniel Schuchardt 2004-09-14 09:02:18 Re: beta1 & beta2 & Windows & heavy load