public inbox for [email protected]  

help / color / mirror / Atom feed

From: Josh Kupershmidt <[email protected]>
To: Louis-Claude Canon <[email protected]>
Cc: [email protected]
Subject: Re: Incomplete compatibility information for triggers
Date: Tue, 13 Nov 2012 23:23:13 -0500
Message-ID: <CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

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?

Josh

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: <CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@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