public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Josh Kupershmidt <[email protected]>
Cc: Louis-Claude Canon <[email protected]>
Cc: [email protected]
Subject: Re: Incomplete compatibility information for triggers
Date: Sat, 23 Feb 2013 00:30:40 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAK3UJRH53ikaqRfubJ9sisgX=eTVvQkd40Bq8RwJ9JeEkeYrYQ@mail.gmail.com>
References: <[email protected]>
<CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@mail.gmail.com>
<[email protected]>
<CAK3UJRH53ikaqRfubJ9sisgX=eTVvQkd40Bq8RwJ9JeEkeYrYQ@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Sun, 2013-01-13 at 14:47 -0700, Josh Kupershmidt wrote:
> 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.
Committed.
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (5+ messages)
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], [email protected]
Subject: Re: Incomplete compatibility information for triggers
In-Reply-To: <[email protected]>
* 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