Message-ID: <E0CB87650B814DFDB14FDCCD010CF3C6@marktestcr.marktest.pt>
From: "Oliveiros d'Azevedo Cristina" <oliveiros.cristina@marktest.pt>
To: "ced" <cedric@dreamgnu.com>
Cc: <pgsql-sql@postgresql.org>
References: <4C28736E.8030409@dreamgnu.com>
	<72B95859322043DF995F2012194B4754@marktestcr.marktest.pt>
	<4C288765.8080604@dreamgnu.com>
	<10B2957382DB4803B59D6ECB7FBCA945@marktestcr.marktest.pt>
	<4C28A6CF.8040304@dreamgnu.com>
Subject: Re: Outer join construction step :strange results
Date: Mon, 28 Jun 2010 14:51:17 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 7bit


>> Can you specify a little more how you represent T1 item sets with this
>> data model?
> (T0.id,T0.fk_T1)=(1,234),(1,235),(1,236)
> 234,235,236 all T1 items and 1 the set of them
>> What exactly represents one row from table T0? A pair (id, fk_T1) ? A
>> set with just one element?
> one item in the set.

That's what I thought in the first place, actually.

But then T0.id cannot be a primary key, because IIRC the primary key 
integrity constraint doesn't allow repeating of values.
And on the example you 've just posted you have three ID = 1

Ain't I Right?

Also, please, do not forget to CC to list, it's always possible that someone 
with more knowledge than me might help you faster

Best,
Oliveiros