Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at> writes:
>> You are absolutely right. The whole point is that either a) everything
>> commits or b) nothing commits.
>> Having some kinds of exceptions allow a partial commit while other
>> exceptions rollback the transaction seems like a very error-prone
>> programming environment to me.
> In this sense a commit is not partial. The commit should commit
> all statements that were not in error.
That interpretation eliminates an absolutely essential capability
(all-or-none behavior) in favor of what strikes me as a very minor
programming shortcut.
> All other DB's behave in this way.
I find this hard to believe, and even harder to believe that it's
mandated by the standard. What you're essentially claiming is that
everyone but us has nested transactions (which'd be the only way to
roll back a single failed statement inside a transaction) and that
SQL92 requires nested transactions --- yet it never uses the phrase nor
makes the obvious step to allowing user-specified nested transactions.
regards, tom lane
