Re: Why can't I put a BEFORE EACH ROW trigger on a view? - Mailing list pgsql-general

From Webb Sprague
Subject Re: Why can't I put a BEFORE EACH ROW trigger on a view?
Date
Msg-id b11ea23c0702241651s78ab8ah9ec98bc815a89c62@mail.gmail.com
Whole thread Raw
In response to Re: Why can't I put a BEFORE EACH ROW trigger on a view?  ("Karl O. Pinc" <kop@meme.com>)
Responses Re: Why can't I put a BEFORE EACH ROW trigger on a view?  ("Webb Sprague" <webb.sprague@gmail.com>)
Re: Why can't I put a BEFORE EACH ROW trigger on a view?  ("Karl O. Pinc" <kop@meme.com>)
List pgsql-general
>.  I have _additional_
> constraints to place on modifications done through
> views, and trickyness involved in modifying the
> underlying tables.

Write a function foo that returns a set, then a view:  "create view as
select * from foo()".  Incorporate all the trickiness in the function,
including variables, multiple temporary tables, whatever you need.

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Why can't I put a BEFORE EACH ROW trigger on a view?
Next
From: "Webb Sprague"
Date:
Subject: Re: Why can't I put a BEFORE EACH ROW trigger on a view?