From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Duplicate constraint names in 7.0.3 |
Date: | 2001-05-08 03:47:14 |
Message-ID: | ECEHIKNFIMMECLEBJFIGCEHMCAAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
OK,
I have modifed heap.c so that it won't automatically generate duplicate
constraint names.
I have _not_ compiled this yet, as it's a bit of a pain for me cos I don't
have bison, etc. However, it looks good to me, and if someone else wants to
test it and then maybe think about if the patch is necessary that's fine by
me.
If no-one wants to test it, I will eventually get around to testing it
myself.
Given that this is my first code patch for Postgres - I should treat it with
caution!
Chris
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Christopher
> Kings-Lynne
> Sent: Friday, 4 May 2001 12:33 PM
> To: Hackers
> Subject: RE: [HACKERS] Duplicate constraint names in 7.0.3
>
>
> > A reasonable interpretation of DROP CONSTRAINT "foo" is to drop *all*
> > constraints named "foo" on the target table.
>
> Then it should probably be a good thing to avoid the automatic
> generation of
> duplicate names? I might take a look at that, actually...
>
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>
Attachment | Content-Type | Size |
---|---|---|
heap.diff | application/octet-stream | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-05-08 04:41:35 | Re: Duplicate constraint names in 7.0.3 |
Previous Message | Bruce Momjian | 2001-05-08 02:37:02 | Re: backend dies on 7.1.1 loading large datamodel. |