Melvin Davidson <melvin6925@xxxxxxxxx> writes: > On Mon, Mar 12, 2018 at 2:26 PM, Steven Roth <steve@xxxxxxxxxxxxxxx> wrote: >> Why does the following code raise an error? >> >> CREATE TABLE ttest (x integer); >> CREATE VIEW vtest AS SELECT x FROM ttest; >> CREATE FUNCTION vtest_insert() RETURNS trigger LANGUAGE plpgsql AS $$ >> RAISE 'foo' USING ERRCODE='unique_violation'; >> END $$; >> 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; >> >> This code raises the error 'foo', even though the insert says DO NOTHING >> and the error type is unique_violation. Why? > *Your problem is that A. TRIGGERS are meant for TABLES, not views* > *and * > *B. You CANNOT insert into a VIEW.* No, instead-of triggers are supposed to do exactly that. The OP's problem is that he imagines that ON CONFLICT works by catching arbitrary errors and checking to see if they are labeled unique_violation. Doesn't work like that; if it did, it'd be the wrong thing, because we would not know whether or how to roll back any other side effects the trigger had had. >> 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? Don't think it's possible unfortunately. The trigger would have to take care of the situation, but it doesn't have any way to know that the calling query has an ON CONFLICT rule. regards, tom lane
