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

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Erwin Brandstetter" <brsaweda(at)gmail(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: There can be only one! How to avoid the "highlander-problem".
Date: 2007-06-05 06:35:06
Message-ID: 87lkeyucx1.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


"Erwin Brandstetter" <brsaweda(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tino Wildenhain 2007-06-05 07:51:59 Re: Encrypted column
Previous Message Simon Riggs 2007-06-05 06:12:20 Re: High-availability