Message-ID: <417D5D49.1090908@onesystem.com>
Date: Mon, 25 Oct 2004 14:08:41 -0600
From: Edmund Bacon <ebacon@onesystem.com>
User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040803)
MIME-Version: 1.0
To: Marinos Yannikos <mjy@geizhals.at>
Cc: pgsql-sql@postgresql.org
Subject: Re: plpgsql: PERFORM vs. SELECT INTO (PERFORM not setting FOUND
References: <417D57B1.8010507@geizhals.at>
In-Reply-To: <417D57B1.8010507@geizhals.at>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Marinos Yannikos wrote:
> (btw.: I'm trying a few ways to ensure that all values in both t1 and t2 
> are unique:
> alter table blup add constraint check (blup_unique3(t1,t2));
>  - perhaps there are more elegant ways, any suggestions?)
>

No doubt someone will tell me this is Very Wrong:

create table blup_text(txt text primary key);

create table blup (t1 text references blup_text(txt),
                    t2 text references blup_text(txt));

You may want to add NOT NULL conditions to t1, t2.

If your text values are long, this may be a good place to use synthetic 
keys - e.g.

create table blup_text(id serial primary key, txt text unique);
create table blup(t1 integer references blup_text(id),
                   t2 integer references blub_text(id));


-- 
Edmund Bacon <ebacon@onesystem.com>