Received: from sss2.sss.pgh.pa.us (root@sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e7719OG10719 for ; Sun, 6 Aug 2000 21:09:24 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id VAA03901; Sun, 6 Aug 2000 21:09:21 -0400 (EDT) To: Itai Zukerman cc: pgsql-sql@postgresql.org Subject: Re: Rules, Select, Union In-reply-to: <87d7jmrmmu.fsf@matt.w80.math-hat.com> References: <87d7jmrmmu.fsf@matt.w80.math-hat.com> Comments: In-reply-to Itai Zukerman message dated "06 Aug 2000 19:32:57 -0400" Date: Sun, 06 Aug 2000 21:09:20 -0400 Message-ID: <3898.965610560@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/47 Itai Zukerman writes: > CREATE RULE data_val AS > ON SELECT TO data > DO INSTEAD > SELECT * FROM pos > UNION > SELECT * FROM neg; IIRC, UNION doesn't work in rules at the moment (a fix is planned for 7.2). But what's the point of splitting the data into the two tables like that? This example is far from compelling, so I wonder whether you shouldn't be considering a schema redesign anyway ... regards, tom lane