From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SET CONSTRAINTS not schema-aware |
Date: | 2003-05-11 20:01:44 |
Message-ID: | 15672.1052683304@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> Peter Eisentraut <peter_e(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-11 20:20:59 | 7.3 and HEAD broken for dropped columns of dropped types |
Previous Message | alex avriette | 2003-05-11 19:13:11 | Re: psql inability to select a socket |