From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Mario Weilguni <mweilguni(at)sime(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: BEGIN inside transaction should be an error |
Date: | 2006-05-11 04:41:35 |
Message-ID: | 4462C07F.5050800@zigo.dhs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane skrev:
> The SQL99 spec does say (in describing START TRANSACTION,
> which is the standard spelling of BEGIN)
>
> 1) If a <start transaction statement> statement is executed when an
> SQL-transaction is currently active, then an exception condition
> is raised: invalid transaction state - active SQL-transaction.
>
> *However*, they are almost certainly expecting that that condition only
> causes the START command to be ignored; not that it should bounce the
> whole transaction.
What is the definition of an "exception condition"?
I thought that it ment that a transaction should fail and that
"completion condition" are
used for warnings that doesn't abort transactions. As an example I
looked up division
by zero in sql99 and it say this:
"If the value of a divisor is zero, then an exception condition
is raised: data exception - division by zero."
Do you mean that some exception conditions fail transactions and some
doesn't?
/Dennis
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2006-05-11 05:11:30 | Warning -- PostgreSQL Anniversary Cutoff Approaching |
Previous Message | Alvaro Herrera | 2006-05-11 04:15:43 | Re: [COMMITTERS] pgsql: Clean up code associated with updating pg_class statistics |
From | Date | Subject | |
---|---|---|---|
Next Message | Tommi Maekitalo | 2006-05-11 06:05:57 | Re: BEGIN inside transaction should be an error |
Previous Message | Luke Lonergan | 2006-05-11 04:16:43 | Re: [PATCH] Improve EXPLAIN ANALYZE overhead by |