Re: [HACKERS] SQL statements: begin and end - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] SQL statements: begin and end
Date
Msg-id Pine.GSO.4.02A.9911231249210.14139-100000@Panda.DoCS.UU.SE
Whole thread Raw
In response to SQL statements: begin and end  (Zeugswetter Andreas SEV <ZeugswetterA@wien.spardat.at>)
List 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@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SEV
Date:
Subject: AW: AW: [HACKERS] Getting OID in psql of recent insert
Next
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] Float/Numeric?