From: Bruce Momjian on
Tom Lane wrote:
> Viktor Valy <vili0121(a)gmail.com> writes:
> > We are 2 Students from the Technical University of Vienna. At our internship
> > we would like to develop the item of the TODO list: "Allow SET CONSTRAINTS
> > to be qualified by schema/table name".
> > Is anyone working on it?
>
> Uh, it was done years ago, AFAICS, unless the Todo entry means something
> non-obvious.
>
> regression=# create schema foo;
> CREATE SCHEMA
> regression=# create table foo.bar (f1 int unique deferrable);
> NOTICE: CREATE TABLE / UNIQUE will create implicit index "bar_f1_key" for table "bar"
> CREATE TABLE
> regression=# set constraints foo.bar_f1_key deferred;
> SET CONSTRAINTS
> regression=# set constraints foo.bar_f1_key immediate;
> SET CONSTRAINTS
> regression=#
>
> Bruce, do you remember what that entry was really about?

Yep, that was it. I have remove that TODO item. Thanks.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers