| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Truncate Triggers |
| Date: | 2008-01-26 16:55:47 |
| Message-ID: | 479B6613.6010707@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Treat wrote:
> 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?
>
>
The rowset (not row) associated with the statement level trigger would
be the whole table in case of a TRUNCATE trigger, so in this (corner)
case it's not too helpful.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2008-01-26 16:57:09 | Re: Truncate Triggers |
| Previous Message | Ivan Voras | 2008-01-26 16:54:17 | Simple row serialization? |