Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA91564 for ; Fri, 27 Aug 1999 10:27:20 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA06711; Fri, 27 Aug 1999 10:26:09 -0400 (EDT) To: Enrico.Scholz@informatik.tu-chemnitz.de cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Inheritance and DELETE In-reply-to: Your message of 27 Aug 1999 02:42:59 +0200 Date: Fri, 27 Aug 1999 10:26:08 -0400 Message-ID: <6709.935763968@sss.pgh.pa.us> From: Tom Lane Enrico.Scholz@informatik.tu-chemnitz.de writes: > CREATE RULE chg_fsO_on_dir_delete AS ON DELETE > TO directory > DO DELETE FROM fsObject* WHERE parent = OLD.fsOid; > But PostgreSQL is complaining with the message > 'ERROR: parser: parse error at or near "*"' Hmm. It looks like the grammar is set up to require a simple relation_name, rather than a relation_expr which would accept *, in DELETE statements. I think this is a bug --- I know no reason that DELETE wouldn't work as an inherited operation. Looks like the fix will take more than a one-line change, though. UPDATE doesn't look like it wants to deal with multiple targets either... regards, tom lane