Re: Hm, table constraints aren't so unique as all that - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Hm, table constraints aren't so unique as all that
Date
Msg-id 20130129134255.GU16126@tamriel.snowman.net
Whole thread Raw
In response to Re: Hm, table constraints aren't so unique as all that  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Peter Geoghegan <peter.geoghegan86@gmail.com> writes:
> > I can see the case for fixing this, but I don't feel that it's
> > particularly important that constraints be uniquely identifiable from
> > the proposed new errdata fields.
>
> I think that we'll soon be buried in gripes if they're not.  Pretty much
> the whole point of this patch is to allow applications to get rid of
> ad-hoc, it-usually-works coding techniques.  I'd argue that not checking
> the entire constraint identity is about as fragile as trying to "sed"
> the constraint name out of a potentially-localized error message.
> In both cases, it often works fine, until the application's context
> changes.

Perhaps I wasn't clear previously, but this is precisely what I had been
argueing for upthread..
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: [sepgsql 2/3] Add db_schema:search permission checks
Next
From: Simon Riggs
Date:
Subject: Re: [sepgsql 2/3] Add db_schema:search permission checks