Re: Preventing Deletions with triggers - Mailing list pgsql-sql

From Tom Lane
Subject Re: Preventing Deletions with triggers
Date
Msg-id 4042.1085153332@sss.pgh.pa.us
Whole thread Raw
In response to Preventing Deletions with triggers  (Jeff Post <POSTJL@milwaukee.k12.wi.us>)
List pgsql-sql
Jeff Post <POSTJL@milwaukee.k12.wi.us> writes:
> CREATE or replace FUNCTION person_fake_delete() RETURNS TRIGGER AS '
>      BEGIN
>          OLD.status := 1; -- This does the fake deletion
>          RETURN NULL;  -- I thought this would prevent the delete from 
> actually happening.
>      END;
> ' LANGUAGE 'plpgsql';

> create trigger person_fake_delete
> before delete on person
> for each row EXECUTE PROCEDURE
> person_fake_delete();

> This however does not work.  the tupple is still deleted from the 
> table.    Any Ideas?

It works for me, in the sense that returning NULL prevents the
deletion.  However that assignment to OLD is a no-op: you can't change
the tuple that way.  You'd have to do something like
UPDATE person SET status = 1 WHERE key = OLD.key;

("key" being whatever your primary key for the table is)
        regards, tom lane


pgsql-sql by date:

Previous
From: Tom Lane
Date:
Subject: Re: Problem with JOINS
Next
From: "Alexander M. Pravking"
Date:
Subject: Memory usage on subselect