----- Original Message -----
From: "Richard Huxton" <dev@archonet.com>
To: "Bruce Momjian" <[EMAIL PROTECTED]>
Cc: "Adnan DURSUN" <[EMAIL PROTECTED]>; <pgsql-hackers@postgresql.org>
Sent: Thursday, January 18, 2007 5:57 PM
Subject: Re: [HACKERS] Temparary disable constraint
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.
Is that not possible that all objects have a column that says whether
object state is ok or not.
When any session wants to try to execute any DML on object, then the
Postgres checks that state column.
If object state is not ok then Postgres raises an exception.
Best Regards
Adnan DURSUN
ASRIN Bilisim Ltd.
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
