Re: SET CONSTRAINTS not schema-aware - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SET CONSTRAINTS not schema-aware
Date
Msg-id 15672.1052683304@sss.pgh.pa.us
Whole thread Raw
In response to Re: SET CONSTRAINTS not schema-aware  (Bruno Wolff III <bruno@wolff.to>)
Responses Re: SET CONSTRAINTS not schema-aware
Re: SET CONSTRAINTS not schema-aware
List pgsql-hackers
Bruno Wolff III <bruno@wolff.to> writes:
>   Peter Eisentraut <peter_e@gmx.net> wrote:
>> SET CONSTRAINTS doesn't allow you to schema-qualify a constraint name.

> I am pretty sure I saw some comments in the discussion about sequence
> naming that constraints are per table and giving them a schema name
> makes no sense. The table they are for has the schema name in it.

Yeah.  We had that discussion at some point during the 7.3 development
cycle, and concluded we liked table-local naming for constraints better
than the SQL spec's global constraint names.

SET CONSTRAINTS still does what it used to do, which is to alter the
behavior of all constraints with the given name.  We should probably
expand the syntax so that a particular table name can be mentioned.
        regards, tom lane



pgsql-hackers by date:

Previous
From: alex avriette
Date:
Subject: Re: psql inability to select a socket
Next
From: Tom Lane
Date:
Subject: 7.3 and HEAD broken for dropped columns of dropped types