From: | Christopher <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | DROP CONSTRAINT patch |
Date: | 2001-05-20 07:50:07 |
Message-ID: | Pine.BSF.4.32.0105201539570.76897-200000@houston.familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
Attached is my patch that adds DROP CONSTRAINT support to PostgreSQL. I
basically want your guys feedback. I have sprinkled some of my q's thru
the text delimited with the @@ symbol. It seems to work perfectly.
At the moment it does CHECK constraints only, with inheritance. However,
due to the problem mentioned before with the mismatching between inherited
constraints it may be wise to disable the inheritance feature for a while.
it is written in an extensible fashion to support future dropping of other
types of constraint, and is well documented.
Please send me your comments, check my use of locking, updating of
indices, use of ERROR and NOTICE, etc. and I will rework the patch based
on feedback until everyone
is happy with it...
Chris
Attachment | Content-Type | Size |
---|---|---|
dropcons.diff | text/plain | 11.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2001-05-20 12:06:55 | Re: External search engine, advice |
Previous Message | mordicus | 2001-05-20 07:47:29 | RE: Re: Functions returning sets |