Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g03NQim85523 for ; Thu, 3 Jan 2002 18:26:44 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g03NQfg01005; Thu, 3 Jan 2002 18:26:42 -0500 (EST) To: Stephan Szabo cc: pgsql-sql@postgresql.org Subject: Re: How to union tables and have a field with UNIQUE constraint? In-reply-to: <20020103134126.Y14151-100000@megazone23.bigpanda.com> References: <20020103134126.Y14151-100000@megazone23.bigpanda.com> Comments: In-reply-to Stephan Szabo message dated "Thu, 03 Jan 2002 13:44:35 -0800" Date: Thu, 03 Jan 2002 18:26:41 -0500 Message-ID: <1002.1010100401@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/27 X-Sequence-Number: 6118 Stephan Szabo writes: >> Since triggers on a view won't do anything either, I don't see how one >> could expect REFERENCES to a view to work. The system ought to reject >> all this stuff as unimplemented. > I think that the insert/update on the fk table will work, but yeah, the > parts on the pk table won't, so that's no good. I wouldn't want to > bother for 7.2, but putting in something to make it so you can't reference > a view is probably a good idea, at least until we can work out a way > to make constraints on views work. Investigation showed that there were a couple of other utility statements that were also missing adequate checks on permissions and table type. I've applied patches. regards, tom lane