| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Adnan DURSUN <a_dursun(at)hotmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Temparary disable constraint |
| Date: | 2007-01-18 15:57:09 |
| Message-ID: | 45AF98D5.8080209@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Adnan DURSUN wrote:
>> Hi, Maybe added more further things to TODO list. Enabled /
>> disabled other objects like view/funtion. imagine a lot of
>> views that referances a table and i wanna drop a column on this
>> table that used by these views. Postgres doesnt allow this.
>> First i must drop these views then drop the column on that
>> table and then recreate these views. Can this be resolved
>> (like oracle does) ?
>
> Not easily, because the view are bound to the object id of the tables
> involved.
The trick would be I think to bind them to individual columns, so if
view V doesn't mention column C then dropping C has no effect on it.
That's a lot more dependencies to track of course.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2007-01-18 15:59:56 | Re: Design notes for EquivalenceClasses |
| Previous Message | Tom Lane | 2007-01-18 15:35:08 | Re: Scanner/Parser question - what does _P imply? |