From: | ced <cedric(at)dreamgnu(dot)com> |
---|---|
To: | Oliveiros d'Azevedo Cristina <oliveiros(dot)cristina(at)marktest(dot)pt> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Outer join construction step :strange results |
Date: | 2010-06-28 14:22:47 |
Message-ID: | 4C28B037.9090000@dreamgnu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
You are right, this is not a correct description.
I'll just in the process of creating a test db to clarify my point and
to produce the symptom.
It'ill me take me some more time, give me an hour or so
thks
cedric
Oliveiros d'Azevedo Cristina wrote:
>
>>> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jerrel Kemper | 2010-06-29 20:51:00 | How to select text field as interger |
Previous Message | Oliveiros d'Azevedo Cristina | 2010-06-28 13:51:17 | Re: Outer join construction step :strange results |