Re: [HACKERS] per-statement-level INSTEAD OF triggers

> It might be more useful after we get the infrastructure that Kevin's been > working on to allow collecting all the updates into a tuplestore that > could be passed to a statement-level trigger. Right now I tend to agree > that there's little point. Maybe, this can be used to re-implement

Re: [HACKERS] per-statement-level INSTEAD OF triggers

Robert Haas writes: > On Mon, Aug 8, 2016 at 4:40 AM, Yugo Nagata wrote: >> I'm asking out of curiosity, do anyone know why we don't have >> per-statement-level INSTEAD OF triggers? I looked into the >> standard SQL (20xx draft), but I can't find the

Re: [HACKERS] per-statement-level INSTEAD OF triggers

On Mon, Aug 8, 2016 at 4:40 AM, Yugo Nagata wrote: > I'm asking out of curiosity, do anyone know why we don't have > per-statement-level INSTEAD OF triggers? I looked into the > standard SQL (20xx draft), but I can't find the restriction > such that INSTEAD OF triggers must

[HACKERS] per-statement-level INSTEAD OF triggers

Hi hackers, I'm asking out of curiosity, do anyone know why we don't have per-statement-level INSTEAD OF triggers? I looked into the standard SQL (20xx draft), but I can't find the restriction such that INSTEAD OF triggers must be row-level. Is there any technical difficulties, or other reasons