From: | J C Lawrence <claw(at)kanga(dot)nu> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | patrick keshishian <patrick(at)pioneerdigital(dot)com>, Charles Tassell <ctassell(at)isn(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: COMMIT after an ERROR? |
Date: | 2001-10-18 07:10:22 |
Message-ID: | 2985.1003389022@kanga.nu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 13 Oct 2001 07:13:25 -0700 (PDT)
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> wrote:
> Well, that's difficult. The spec is very hard to understand about
> that. I believe we determined that our behavior was very very
> close to complient, but that it does not match the standard
> reading of that section.
My reading of the spec came out as:
The spec in regard to exact behaviour at COMMIT in the presence of
errors is, in spec language, "undefined".
The current PostgresQL behaviour doesn't violate the spec, but is
also one of many possible mutually contradictory behaviours (such
as not rolling back on error) that don't appear to violate the
spec.
Ahh well, its not like inserting explicit ROLLBACKs is that hard.
--
J C Lawrence
---------(*) Satan, oscillate my metallic sonatas.
claw(at)kanga(dot)nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
From | Date | Subject | |
---|---|---|---|
Next Message | Dr. Evil | 2001-10-18 07:16:19 | Re: TEXT field's length limit in PostgreSQL |
Previous Message | Michał 'Samuel' Modestowicz | 2001-10-18 06:48:07 | TEXT field's length limit in PostgreSQL |