Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f31JZ8K39948 for ; Sun, 1 Apr 2001 15:35:08 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f31JYtw00449; Sun, 1 Apr 2001 15:34:55 -0400 (EDT) To: "J.Fernando Moyano" cc: pgsql-sql@postgresql.org Subject: Re: ON DELETE rule In-reply-to: <01040110093800.01615@txino.mikasa.eh> References: <01040110093800.01615@txino.mikasa.eh> Comments: In-reply-to "J.Fernando Moyano" message dated "Sun, 01 Apr 2001 10:09:38 +0200" Date: Sun, 01 Apr 2001 15:34:55 -0400 Message-ID: <446.986153695@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/5 X-Sequence-Number: 2344 "J.Fernando Moyano" writes: > I'm trying to do something like this: > CREATE RULE piezas_delete AS > ON delete TO piezas > DO update materia_prima set usadas=(usadas-1) > where n_material=old.n_material; > The rule is created. OK .... but the action doesn't run like it's supossed. This will almost certainly not do what you intended, at least not for cases in which a DELETE deletes multiple rows from piezas. The rule creates an additional query that will be run once for each DELETE query against piezas. You appear to be envisioning one firing per tuple deleted. I'd recommend doing the UPDATE inside a trigger instead. That approach will operate in the way you envision. regards, tom lane