From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, 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-15 03:13:48 |
Message-ID: | 200305150313.h4F3Dms01854@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.
Is this a TODO?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-15 03:24:42 | Re: SET CONSTRAINTS not schema-aware |
Previous Message | Bruce Momjian | 2003-05-15 03:09:32 | Win32, compiles, under, MinGW/Msys! |