On Tue, Mar 13, 2018 at 6:47 AM, Melvin Davidson <melvin6...@gmail.com>
> On Mon, Mar 12, 2018 at 2:26 PM, Steven Roth <st...@rothskeller.net>
>> This code raises the error 'foo', even though the insert says DO NOTHING
>> and the error type is unique_violation. Why?
>> More generally: how can one write trigger functions for a view (that is
>> not automatically updatable), such that INSERT ... ON CONFLICT DO UPDATE
>> will work with the correct semantics? What can one do in the INSERT
>> trigger that will cause PostgreSQL to execute the caller-supplied UPDATE
Sorry, not sure...
> >CREATE TRIGGER vtest_insert INSTEAD OF INSERT ON *vtest*
> > FOR EACH ROW EXECUTE PROCEDURE vtest_insert();
> >*INSERT INTO vtest *VALUES (1) ON CONFLICT DO NOTHING;
> *Your problem is that A. TRIGGERS are meant for TABLES, not views*
> *and *
> *B. You CANNOT insert into a VIEW.*
Your knowledge is this area is out-of-date...you should read the page you
linked to again.
I'll admit "table_name" probably could be labelled "relation_name"...though
that is then too broad.