On Sat, 2005-12-03 at 23:00 +, Rodrigo Madera wrote:
> CREATE TABLE person(
>id bigint PRIMARY KEY,
>first_name TEXT,
>age INT,
>mother bigint REFERENCES person,
>father biging REFERENCES person,
>siblings array of bigints (don't remember the syntax, but you get the
>
On Sat, 3 Dec 2005 23:00:21 +, Rodrigo Madera <[EMAIL PROTECTED]> wrote:
> Imagine a table named Person with "first_name" and "age".
>
> Now let's make it fancy and put a "mother" and "father" field that is
> a reference to the own table (Person). And to get even fuzzier, let's
> drop in some
Hélder M. Vieira wrote:
- Original Message - From: "Andreas Pflug"
<[EMAIL PROTECTED]>
Create a table "sibling" with parent_id, sibling_id and appropriate
FKs, allowing the model to reflect the relation. At the same time, you
can drop "mother" and "father", because this relation is
- Original Message -
From: "Andreas Pflug" <[EMAIL PROTECTED]>
Create a table "sibling" with parent_id, sibling_id and appropriate FKs,
allowing the model to reflect the relation. At the same time, you can drop
"mother" and "father", because this relation is covered too
Something
Rodrigo Madera wrote:
Imagine a table named Person with "first_name" and "age".
Now let's make it fancy and put a "mother" and "father" field that is
a reference to the own table (Person). And to get even fuzzier, let's
drop in some siblings:
CREATE TABLE person(
id bigint PRIMARY KEY,
fir
Imagine a table named Person with "first_name" and "age".
Now let's make it fancy and put a "mother" and "father" field that is
a reference to the own table (Person). And to get even fuzzier, let's
drop in some siblings:
CREATE TABLE person(
id bigint PRIMARY KEY,
first_name TEXT,
age IN
