Received: from ant.utdt ([200.41.62.131]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA64046 for ; Fri, 12 Nov 1999 10:31:31 -0500 (EST) (envelope-from mig@utdt.edu) Resent-From: mig@utdt.edu Received: (from mig@localhost) by ant.utdt (8.8.7/8.8.7) id MAA07053 for pgsql-sql@postgresql.org; Fri, 12 Nov 1999 12:28:17 -0300 Resent-Message-Id: <199911121528.MAA07053@ant.utdt> Message-Id: <199911121528.MAA07053@ant.utdt> X-Authentication-Warning: ant.utdt: mig set sender to Miguel Sofer using -f Resent-Date: 12 Nov 1999 12:28:17 -0300 Resent-To: pgsql-sql@postgresql.org Date: 12 Nov 1999 12:13:55 -0300 From: " To: pgsql-sql@postgresql.org Subject: Rules and referential integrity I seem to have found a way to use the rule system for referential integrity checks. The manual says (in the "Rules vs Triggers part) "It is possible, to place a qualified rule that rewrites a query to NOTHING if the value of a column does not appear in another table. But then the data is silently thrown away and that's not a good idea. If checks for valid values are required, and in the case of an invalid value an error message should be generated, it must be done by a trigger for now." Now: why not define a function (in pltcl; could be something else?) create function err(bpchar) returns bpchar as 'error $1' language 'pltcl' Then, if the value of a column does not appear in another table, you could rewrite the query to (for instance) select err('your message') This will raise a PGRES_FATAL_ERROR , with error message ERROR: pltcl: your message So: it is possible. Why it is better (or worse) than a trigger, I do not know. Views on that?