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

From Gregory Stark
Subject Re: There can be only one! How to avoid the "highlander-problem".
Date
Msg-id 87lkeyucx1.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: There can be only one! How to avoid the "highlander-problem".  (Erwin Brandstetter <brsaweda@gmail.com>)
Responses Re: There can be only one! How to avoid the "highlander-problem".  (Erwin Brandstetter <brsaweda@gmail.com>)
List pgsql-general
"Erwin Brandstetter" <brsaweda@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 :)

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?

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


pgsql-general by date:

Previous
From: "Erick Papadakis"
Date:
Subject: Database design wisdom needed
Next
From: Chander Ganesan
Date:
Subject: Re: High-availability