public inbox for [email protected]
help / color / mirror / Atom feedFrom: Josh Kupershmidt <[email protected]>
To: Louis-Claude Canon <[email protected]>
Cc: [email protected]
Subject: Re: Incomplete compatibility information for triggers
Date: Sun, 13 Jan 2013 14:47:14 -0700
Message-ID: <CAK3UJRH53ikaqRfubJ9sisgX=eTVvQkd40Bq8RwJ9JeEkeYrYQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Wed, Nov 14, 2012 at 2:19 PM, Louis-Claude Canon
<[email protected]> wrote:
> Le 14/11/2012 05:23, Josh Kupershmidt a écrit :
>
>> On Sun, Nov 11, 2012 at 3:52 PM, Louis-Claude Canon
>> <[email protected]> wrote:
>>
>>> the compatibility section of the "create trigger" page
>>> (http://www.postgresql.org/docs/devel/static/sql-createtrigger.html)
>>> claims
>>> that a missing functionality is the ability to define aliases for the
>>> "old"
>>> and "new" rows or tables. If I am understanding this correctly, another
>>> related missing functionality is that PostgreSQL does not allow the old
>>> and
>>> new tables to be referenced for statement-level triggers (i.e., the "OLD
>>> TABLE" that contains all the deleted/modified rows in case of
>>> deletion/update). I think this is also worth noting as any workaround for
>>> it
>>> seems to be more difficult (if possible at all) than for the missing
>>> alias
>>> feature.
>>
>> +1, it seems like a useful missing piece from the SQL:2011 standard.
>> Care to send a documentation patch?
>
>
> Let me know if it requires a second round.
A (belated) +1 for this patch. There were two small typos which I've
fixed in the attached version. You may want to add this patch soon to
the 2013-01 CommitFest so it doesn't get lost.
> By the way, I can propose another patch regarding the transaction isolation
> relatively to my previous post on pgsql-bugs.
If that doc change hasn't been made yet, you may want to post a patch.
Josh
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Attachments:
[application/octet-stream] 0002-Document-the-missing-OLD-NEW-TABLE-trigger-feature.patch (1.6K, 2-0002-Document-the-missing-OLD-NEW-TABLE-trigger-feature.patch)
download | inline diff:
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
new file mode 100644
index 0f87b1f..49a8130
*** a/doc/src/sgml/ref/create_trigger.sgml
--- b/doc/src/sgml/ref/create_trigger.sgml
*************** CREATE TRIGGER view_insert
*** 484,494 ****
<para>
The <command>CREATE TRIGGER</command> statement in
<productname>PostgreSQL</productname> implements a subset of the
! <acronym>SQL</> standard. The following functionality is currently missing:
<itemizedlist>
<listitem>
<para>
SQL allows you to define aliases for the <quote>old</quote>
and <quote>new</quote> rows or tables for use in the definition
of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
--- 484,505 ----
<para>
The <command>CREATE TRIGGER</command> statement in
<productname>PostgreSQL</productname> implements a subset of the
! <acronym>SQL</> standard. The following functionalities are currently
! missing:
<itemizedlist>
<listitem>
<para>
+ <productname>PostgreSQL</productname> does not allow the old and new
+ tables to be referenced for statement-level triggers (i.e., the tables
+ that contain all the old and/or new rows, which are referred to as
+ <literal>OLD TABLE</literal> and <literal>NEW TABLE</literal> in the
+ <acronym>SQL</> standard).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
SQL allows you to define aliases for the <quote>old</quote>
and <quote>new</quote> rows or tables for use in the definition
of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Incomplete compatibility information for triggers
In-Reply-To: <CAK3UJRH53ikaqRfubJ9sisgX=eTVvQkd40Bq8RwJ9JeEkeYrYQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox