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

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: There can be only one! How to avoid the "highlander-problem".
Дата
Msg-id 87lkeyucx1.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: There can be only one! How to avoid the "highlander-problem".  (Erwin Brandstetter <brsaweda@gmail.com>)
Ответы Re: There can be only one! How to avoid the "highlander-problem".  (Erwin Brandstetter <brsaweda@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: "Erick Papadakis"
Дата:
Сообщение: Database design wisdom needed
Следующее
От: Chander Ganesan
Дата:
Сообщение: Re: High-availability