Re: Incomplete compatibility information for triggers

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Louis-Claude Canon <louis-claude(dot)canon(at)femto-st(dot)fr>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: Incomplete compatibility information for triggers
Date: 2012-11-14 04:23:13
Message-ID: CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sun, Nov 11, 2012 at 3:52 PM, Louis-Claude Canon
<louis-claude(dot)canon(at)femto-st(dot)fr> 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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Louis-Claude Canon 2012-11-14 21:19:39 Re: Incomplete compatibility information for triggers
Previous Message Josh Kupershmidt 2012-11-14 03:49:12 Re: pg_dump -t '"Table"' for cmd.exe