Re: insert/update/delete returning and rules - Mailing list pgsql-hackers

From Zeugswetter Andreas DCP SD
Subject Re: insert/update/delete returning and rules
Date
Msg-id E1539E0ED7043848906A8FF995BDA579014DC05E@m0143.s-mxs.net
Whole thread Raw
In response to Re: insert/update/delete returning and rules  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> With this approach, you still have to update your rules if
> you want to support RETURNING on your views --- but if you
> don't update them, you don't have a security hole.  Basically
> the standard setup for an updatable view would use
>     "ON INSERT DO INSTEAD INSERT INTO ... RETURNING ..."
> where today you don't write any RETURNING.

I like that approach. And if the sections allow CASE WHEN
it should be possible to cover all use cases efficiently.

Andreas


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCHES] Documentation fix for --with-ldap
Next
From: Michael Glaesemann
Date:
Subject: Re: [PATCHES] possible ecpg vpath build error