Re: Truncate Triggers - Mailing list pgsql-hackers

From Robert Treat
Subject Re: Truncate Triggers
Date
Msg-id 200801261119.13842.xzilla@users.sourceforge.net
Whole thread Raw
In response to Truncate Triggers  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Truncate Triggers  (Gregory Stark <stark@enterprisedb.com>)
Re: Truncate Triggers  (Andreas Pflug <pgadmin@pse-consulting.de>)
Re: Truncate Triggers  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Truncate Triggers  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Friday 25 January 2008 06:40, Simon Riggs wrote:
> Notes: As the syntax shows, these would be statement-level triggers
> (only). Requesting row level triggers will cause an error. [As Chris
> Browne explained, if people really want, they can use these facilities
> to create a Before Statement trigger that executes a DELETE, which then
> fires row level calls.]
>

This seems to completly hand-wave away the idea of implementing row level 
visibility in statement level triggers, something I am hoping to see 
implemented somewhere down the line. Am I missing something?

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL


pgsql-hackers by date:

Previous
From: "Gevik Babakhani"
Date:
Subject: Re: PostgreSQL Programmer's Guide Books
Next
From: Gregory Stark
Date:
Subject: Re: Truncate Triggers