From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Viktor Valy <vili0121(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, chris(dot)gut(at)gmx(dot)at |
Subject: | Re: Develop item from TODO list |
Date: | 2010-08-04 12:06:37 |
Message-ID: | 201008041206.o74C6b314196@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Viktor Valy <vili0121(at)gmail(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-08-04 12:09:51 | Re: merge command - GSoC progress |
Previous Message | Florian Pflug | 2010-08-04 11:58:32 | Re: Patch to show individual statement latencies in pgbench output |