From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org>, "'Bruce Momjian'" <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: [HACKERS] SQL statements: begin and end |
Date: | 1999-11-23 11:52:16 |
Message-ID: | Pine.GSO.4.02A.9911231249210.14139-100000@Panda.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Whatever happened to
BEGIN TRANSACTION;
...
COMMIT;
I never liked END to begin with, since it doesn't really imply that you
are committing anything. Or what is the non-committing counterpart of END?
But I think we should go strictly with the SQL standard, even if that
contradicts what I just said. (?)
-Peter
On Tue, 23 Nov 1999, Zeugswetter Andreas SEV wrote:
> I see everybody using the following PostgreSQL statements:
>
> "begin" instead of "begin work"
> "end" instead of "commit work"
>
> This is really bad, because it is not standard, and can easily be taken for
> a statement block, which it is definitely not ! It is a transaction block.
>
> I vote for issuing a NOTICE for these in V7 and remove them in V8,
> at least the single "end"
>
> Bruce, please don't use "begin" and "end" in your book.
>
> Andreas
>
> ************
>
>
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 1999-11-23 14:20:37 | Re: [HACKERS] Float/Numeric? |
Previous Message | Zeugswetter Andreas SEV | 1999-11-23 10:37:25 | AW: AW: [HACKERS] Getting OID in psql of recent insert |