From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Alex Pilosov <alex(at)pilosoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_depend |
Date: | 2001-07-18 03:08:15 |
Message-ID: | 3.0.5.32.20010718130815.03071200@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 11:25 18/07/01 +0900, Hiroshi Inoue wrote:
>
>Oops I made a mistake.
>Reference name is needed not an object name,
>i.e
> object relid
> object oid
> relerence relid
> reference oid
> reference name
>
I think any deisgn needs to cater for attr dependencies. eg.
create table a (f1 int4, f2 int8);
create view view_a as select f2 from a;
Then
alter table a drop f1; -- Is OK. Should just happen
alter table a drop f2; -- Should warn about the view, and/or cascade etc.
alter table a alter f2 float; -- Should trigger a view recompilation.
...same thing needs to happen with constraints that reference attrs
I *think* tables are the only items that can have subobjects with dependant.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | will trillich | 2001-07-18 03:42:48 | Re: psql -l |
Previous Message | Bruce Momjian | 2001-07-18 02:29:54 | Re: pg_depend |