| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug of ALTER TABLE DROP CONSTRAINT |
| Date: | 2009-04-07 14:53:39 |
| Message-ID: | 1935.1239116019@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Nikhil Sontakke wrote:
>> Warrants an entry in the TODO items list:
>>
>> * make NOT NULL constraints have pg_constraint entries, just like CHECK
>> constraints
> This is now a TODO item (I just updated the description):
> Store the constraint names of NOT NULL constraints
I was intending to do that yesterday, but lost interest after
discovering how many duplicate, obsolete, and/or mutually contradictory
TODO entries there are related to constraints. That needs to be cleaned
up and consolidated sometime.
Also, what is wrong with the precise statement of the TODO item that
Nikhil gave? The one you gave would encourage someone to waste time on
a 100% wrong implementation (like adding a constraint name column to
pg_attribute).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2009-04-07 15:07:56 | Re: [HACKERS] string_to_array with empty input |
| Previous Message | Bruce Momjian | 2009-04-07 14:45:13 | Re: Bug of ALTER TABLE DROP CONSTRAINT |