Re: Temparary disable constraint

Maybe you are right as technically but this behaver causes a lot
of maintance problem on a database that alot of view and functions that
depends on a table or a type. I think objects has a property if that object
is enable or not. We hope this problem can be resolved at 8.4 release.

Best Regards

Adnan DURSUN
ASRIN Bilisim Ltd.

----- Original Message -----
From: "Bruce Momjian" <bruce(at)momjian(dot)us>
To: "Adnan DURSUN" <a_dursun(at)hotmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Wednesday, January 17, 2007 5:49 PM
Subject: Re: [HACKERS] Temparary disable constraint

> 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.
>
> --
> Bruce Momjian bruce(at)momjian(dot)us
> EnterpriseDB http://www.enterprisedb.com
>
> + If your life is a hard drive, Christ can be your backup. +
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>