From: Jens Hartwig <jens.hartwig@t-systems.de>
To: PSQL-Sql \(E-Mail\) <pgsql-sql@postgresql.org>
Subject: Problems with RULE
Date: Tue, 6 Mar 2001 08:11:48 +0100
Message-ID: <001f01c0a60c$b6976f50$c10ac98a@0000864A433A> (raw)
Hello all,
I tried to implement the following rule: if someone wants to delete a record
from a table t_xyz (id integer, deleted boolean) the record should get a
delete-flag (deleted = true). When this "pre-deleted" record is deleted for
the next time it should be physically deleted from the database.
I implemented the following rule:
CREATE RULE r_del_xyz
AS ON DELETE TO t_xyz WHERE (old.deleted = false)
DO INSTEAD
UPDATE t_xyz
SET deleted = true
WHERE id = old.id;
Now I tested the new rule:
INSERT INTO t_xyz VALUES (1, false);
INSERT INTO t_xyz VALUES (2, false);
DELETE FROM t_xyz WHERE id = 1;
SELECT * FROM t_xyz ;
id | deleted
----+---------
2 | f
What has happened? The rule seems to be ignored and the record was deleted!
I dropped the rule, deleted all records and recreated the rule without the
additional WHERE-Clause in the UPDATE-Statement:
DROP RULE r_del_xyz;
DELETE FROM t_xyz;
CREATE RULE r_del_xyz
AS ON DELETE TO t_xyz WHERE (old.deleted = false)
DO INSTEAD
UPDATE t_xyz
SET deleted = true;
INSERT INTO t_xyz VALUES (1, false);
INSERT INTO t_xyz VALUES (2, false);
The same test again:
DELETE FROM t_xyz WHERE id = 1;
SELECT * FROM t_xyz ;
id | deleted
----+---------
2 | t
It seems to me that PostgreSQL executed the rule, but ignored the keyword
INSTEAD and deleted the record after having updated it?!
One last test with a slightly different rule (look at the WHERE-clause in
the "AS-ON"-clause):
DROP RULE r_del_xyz;
DELETE FROM t_xyz;
CREATE RULE r_del_xyz
AS ON DELETE TO t_xyz WHERE (1 = 1)
DO INSTEAD
UPDATE t_xyz
SET deleted = true
WHERE id = old.id;
INSERT INTO t_xyz VALUES (1, false);
INSERT INTO t_xyz VALUES (2, false);
DELETE FROM t_xyz WHERE id = 1;
SELECT * FROM t_xyz ;
id | deleted
----+---------
2 | f
1 | t
DELETE FROM t_xyz WHERE id = 1;
SELECT * FROM t_xyz ;
Everything is alright now! Am I wrong? Is the WHERE-clause "WHERE
(old.deleted = false)" not correct? Any hints? Or it is really a bug?
Best regards, Jens Hartwig
PS: You will find the scripts in the attachment.
-----------------------------------------------------
T-Systems
Projektleiter
debis Systemhaus GEI GmbH
Hausanschrift: Eichhornstraße 3, 10785 Berlin
Postanschrift: 10785 Berlin
Telefon: (004930) 25 54-32 82
Telefax: (004930) 25 54-31 87
Mobiltelefon: (0170) 167 26 48
E-Mail: jens.hartwig@t-systems.de
Internet: http://www.t-systems.deAttachments:
rule_error_1.sql (application/octet-stream, 385B) download
rule_error_2.sql (application/octet-stream, 365B) download
rule_error_3.sql (application/octet-stream, 375B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: jens.hartwig@t-systems.de
Subject: Re: Problems with RULE
In-Reply-To: <001f01c0a60c$b6976f50$c10ac98a@0000864A433A>
References: <001f01c0a60c$b6976f50$c10ac98a@0000864A433A>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox