From: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bug of ALTER TABLE DROP CONSTRAINT |
Date: | 2009-04-03 09:45:22 |
Message-ID: | a301bfd90904030245g1a8e113cu17ec902de3fe9ad6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> We've discussed before the idea that NOT NULL constraints should be
> explicitly represented in pg_constraint, just like general CHECK
> constraints (this would allow them to be named, have sane inheritance
> behavior, etc). If we had that, then pg_attribute.attnotnull could
> indicate the OR of "there is a NOT NULL on this column" and "there is
> a pkey constraint on this column", and you'd just have to recompute it
> properly after dropping either kind of constraint.
>
> Not happening for 8.4, but maybe someday someone will get around to it.
>
Warrants an entry in the TODO items list:
* make NOT NULL constraints have pg_constraint entries, just like CHECK
constraints
Regards,
Nikhils
--
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | shrish purohit | 2009-04-03 11:51:07 | Expression based index |
Previous Message | Zeugswetter Andreas OSB sIT | 2009-04-03 08:40:58 | Re: Abwesend: [GENERAL] string_to_array with empty input |