Re: There can be only one! How to avoid the "highlander-problem". - Mailing list pgsql-general

From Erwin Brandstetter
Subject Re: There can be only one! How to avoid the "highlander-problem".
Date
Msg-id 1181050601.303066.87390@o5g2000hsb.googlegroups.com
Whole thread Raw
In response to Re: There can be only one! How to avoid the "highlander-problem".  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-general
On Jun 5, 8:35 am, s...@enterprisedb.com (Gregory Stark) wrote:
> "Erwin Brandstetter" <brsaw...@gmail.com> writes:
> > I postulate further that a king only be king of his own people (rules out
> > multiple kingships, too).
>
> That's not how it's worked in the past :)

Yeah i know. :) That's why I had to postulate this one explicitly.


> If you have a nation table wouldn't you just have a king_id column in that
> table which is a foreign key reference to man_id?

Have a look at my model 3.) above ..

Regards
Erwin


pgsql-general by date:

Previous
From: "Bhavana.Rakesh"
Date:
Subject: Re: jdbc pg_hba.conf error
Next
From: Ron Johnson
Date:
Subject: Re: Database design wisdom needed