Received: from dragon.klte.hu (dragon.klte.hu [193.6.138.65]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g047tWm12396 for ; Fri, 4 Jan 2002 02:55:33 -0500 (EST) (envelope-from katonag@dragon.klte.hu) Received: from localhost (katonag@localhost) by dragon.klte.hu (8.9.3/8.9.3) with ESMTP id JAA05113 for ; Fri, 4 Jan 2002 09:08:51 +0100 (MET) Date: Fri, 4 Jan 2002 09:08:50 +0100 (MET) From: Katona Gabor X-Sender: katonag@dragon To: pgsql-sql@postgresql.org Subject: Re: How to union tables and have a field with UNIQUE constraint? In-Reply-To: <15666.1010091097@sss.pgh.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200201/93 X-Sequence-Number: 6182 > 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 :) ? And thanks for the answers. Gabor Katona