Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA19974 for ; Mon, 27 Sep 1999 15:47:54 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id PAA12964; Mon, 27 Sep 1999 15:44:49 -0400 (EDT) From: Bruce Momjian Message-Id: <199909271944.PAA12964@candle.pha.pa.us> Subject: Re: [SQL] Inheritance and DELETE In-Reply-To: <6709.935763968@sss.pgh.pa.us> from Tom Lane at "Aug 27, 1999 10:26:08 am" To: Tom Lane Date: Mon, 27 Sep 1999 15:44:48 -0400 (EDT) CC: Enrico.Scholz@informatik.tu-chemnitz.de, pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > 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... Added to TODO list: * Allow DELETE and UPDATE to use inheritance using tablename* -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026