That looks like a good solution. And that way it won't cascade. Thanks
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Huxton Sent: May 11, 2005 11:53 AM To: Mark Borins Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Disabling Triggers Mark Borins wrote: > I am creating a system where I have a trigger on three different tables. > There is a particular Boolean field in each of these tables that when it is > set in table it should be set the same in the other two. Just make sure you only check the boolean value too: -- Trigger on table a does: IF NEW.my_bool=OLD.my_bool THEN RETURN NEW; END IF; UPDATE b SET my_bool=NEW.my_bool WHERE id=NEW.something AND my_bool <> NEW.my_bool UPDATE c SET my_bool=NEW.my_bool WHERE id=NEW.something AND my_bool <> NEW.my_bool -- End code That way, you always do the minimal amount of work anyway. -- Richard Huxton Archonet Ltd ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
