Re: Temparary disable constraint - Mailing list pgsql-hackers

From Richard Huxton
Subject Re: Temparary disable constraint
Date
Msg-id 45AF98D5.8080209@archonet.com
Whole thread Raw
In response to Re: Temparary disable constraint  (Bruce Momjian <bruce@momjian.us>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Scanner/Parser question - what does _P imply?
Next
From:
Date:
Subject: Re: Scanner/Parser question - what does _P imply?