RE: Duplicate constraint names in 7.0.3 - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject RE: Duplicate constraint names in 7.0.3
Date
Msg-id ECEHIKNFIMMECLEBJFIGCEHMCAAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to RE: Duplicate constraint names in 7.0.3  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: Duplicate constraint names in 7.0.3  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Duplicate constraint names in 7.0.3  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.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

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: MULTIBYTE and SQL_ASCII (was Re: [JDBC] Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars?)
Next
From: Bruce Momjian
Date:
Subject: Re: Duplicate constraint names in 7.0.3