Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0C0q3B65538 for ; Fri, 11 Jan 2002 19:52:03 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 387DBD5F7; Fri, 11 Jan 2002 16:51:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 2A2705BF4; Fri, 11 Jan 2002 16:51:56 -0800 (PST) Date: Fri, 11 Jan 2002 16:51:56 -0800 (PST) From: Stephan Szabo To: Katona Gabor Cc: Subject: Re: How to union tables and have a field with UNIQUE constraint? In-Reply-To: Message-ID: <20020111165115.D97125-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200201/103 X-Sequence-Number: 6192 On Fri, 4 Jan 2002, Katona Gabor wrote: > > > > I would argue that this should be disallowed, since it does not do > > anything useful and can only mislead people into thinking that it > > has some effect. > > > > 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. > > OK, I understand the problem with referencing a view and I changed my code > to use CREATE TABLE AS instead of a view (the created table will change very > rarely, so I'll update it then via a trigger). Is this way ok now and will > work until the end of time :) ? That doesn't sound like something that'll stop working, so you should be safe.