Jeff Post <POSTJL(at)milwaukee(dot)k12(dot)wi(dot)us> writes:
> CREATE or replace FUNCTION person_fake_delete() RETURNS TRIGGER AS '
> OLD.status := 1; -- This does the fake deletion
> RETURN NULL; -- I thought this would prevent the delete from
> actually happening.
> ' LANGUAGE 'plpgsql';
> create trigger person_fake_delete
> before delete on person
> for each row EXECUTE PROCEDURE
> 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
In response to
pgsql-sql by date
|Next:||From: Alexander M. Pravking||Date: 2004-05-22 17:54:19|
|Subject: Memory usage on subselect|
|Previous:||From: Tom Lane||Date: 2004-05-21 15:05:28|
|Subject: Re: Problem with JOINS |