Re: set constraints docs page

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: set constraints docs page
Date: 2003-08-19 12:08:20
Message-ID: 005201c3664a$9518f640$6401a8c0@DUNSLANE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


----- Original Message -----
From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Stephan Szabo" <sszabo(at)megazone(dot)bigpanda(dot)com>; "Hackers"
<pgsql-hackers(at)postgresql(dot)org>
Sent: Tuesday, August 19, 2003 3:51 AM
Subject: Re: [HACKERS] set constraints docs page

> Christopher Kings-Lynne writes:
>
> > > > It's a constraint name. IIRC, it happens to affect all such named
> > > > constraints currently. We should probably allow
<tablename>.<constraint>
> > > > (and <schema>.<tablename>.<constraint>) as well. Too late for 7.4,
but
> > > > this can happen for 7.5 if there aren't any objections.
> > >
> > > I object.
> >
> > Thanks for the helpful objection. To what do you object specifically
and
> > why?
>
> I object to creating gratuitous incompatibilities with the SQL standard,
> which will obstruct legitimate features down the road. The SQL standard
> says it is <schema>.<constraint>.
>

Is there a case for enforcing uniqueness on constraint names, then?

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shridhar Daithankar 2003-08-19 12:31:33 Re: Buglist
Previous Message Bo Lorentsen 2003-08-19 11:32:00 Buglist