From: | sferac(at)bo(dot)nettuno(dot)it |
---|---|
To: | Zeugswetter Andreas <andreas(dot)zeugswetter(at)telecom(dot)at> |
Cc: | "'Michael Meskes'" <meskes(at)topsystem(dot)de>, "'pgsql-hackers(at)hub(dot)org'" <pgsql-hackers(at)hub(dot)org> |
Subject: | Re: AW: [HACKERS] Begin statement again |
Date: | 1998-03-13 17:28:31 |
Message-ID: | Pine.LNX.3.96.980313172800.1783A-100000@nero |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 13 Mar 1998, Zeugswetter Andreas wrote:
> I think we should depreciate the BEGIN/END keywords in SQL to allow them
> to be used for the new PL/SQL. So definitely leave them out of ecpg now.
> Only accept BEGIN WORK and BEGIN TRANSACTION. (do a sequence of commit work; begin work)
Apologies for intrusion.
I think we don't need BEGIN/END at all, these statements aren't SQL standard.
END is an alias for COMMIT.
(why do we need two statements to do the same thing?).
from man commit:
"...
This commands commits the current transaction. All
changes made by the transaction become visible to others
and are guaranteed to be durable if a crash occurs.
COMMIT is functionally equivalent to the END command"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
from man begin:
"...
commands commits the current transaction. All
changes made by the transaction become visible to others
and are guaranteed to be durable if a crash occurs."
and BEGIN should be changed to SQL standard SET TRANSACTION statement.
-------
PS:
I think PL/pgSQL is an eccellent idea. Go for it.
Ciao, Jose'
From | Date | Subject | |
---|---|---|---|
Next Message | Darren King | 1998-03-13 17:39:24 | Re: [HACKERS] suspected problem with cache updates |
Previous Message | Jan Wieck | 1998-03-13 17:17:17 | Re: [HACKERS] suspected problem with cache updates |