Tom Lane wrote:
>
> Steve Wampler <[EMAIL PROTECTED]> writes:
> > Well, it looks like I got bit by this after all. Can someone show
> > me a rule to attach to a view ("attributes") to invoke a trigger function
> > (insert_or_update)?
>
> > The trigger function maps the update into either an ins
Tom Lane wrote:
>
> Steve Wampler <[EMAIL PROTECTED]> writes:
> > One of the listed bug fixes is:
> >Disallow INSERT/UPDATE/DELETE on views
> > Can some one give me a little insight on what this
> > implies?
>
> It means that if you try to do INSERT/UPDATE/DELETE on a view that
> doesn't hav
Steve Wampler <[EMAIL PROTECTED]> writes:
> Well, it looks like I got bit by this after all. Can someone show
> me a rule to attach to a view ("attributes") to invoke a trigger function
> (insert_or_update)?
> The trigger function maps the update into either an insert or an update
> on the under
Steve Wampler <[EMAIL PROTECTED]> writes:
> One of the listed bug fixes is:
>Disallow INSERT/UPDATE/DELETE on views
> Can some one give me a little insight on what this
> implies?
It means that if you try to do INSERT/UPDATE/DELETE on a view that
doesn't have a rule to translate that action t
One of the listed bug fixes is:
Disallow INSERT/UPDATE/DELETE on views
Can some one give me a little insight on what this
implies?
In particular, I currently (pg 7.0.3) have views with
trigger functions on insert and update that trap the
action and recast it to a table (after doing some che
