From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Katona Gabor <katonag(at)dragon(dot)klte(dot)hu> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: How to union tables and have a field with UNIQUE constraint? |
Date: | 2002-01-12 00:51:56 |
Message-ID: | 20020111165115.D97125-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Murray Prior Hobbs | 2002-01-12 13:41:17 | triggered data change violation |
Previous Message | Tom Lane | 2002-01-11 22:01:04 | Re: who has lock on table/row |