Re: Enforce primary key on every table during dev?

Поиск
Список
Период
Сортировка
От Ron Johnson
Тема Re: Enforce primary key on every table during dev?
Дата
Msg-id d29c9c67-1b12-68f1-2fd8-3cc28971fd9d@cox.net
обсуждение исходный текст
Ответ на Re: Enforce primary key on every table during dev?  (Alban Hertroys <haramrae@gmail.com>)
Ответы Re: Enforce primary key on every table during dev?
Список pgsql-general
On 03/01/2018 03:14 PM, Adrian Klaver wrote:
On 03/01/2018 01:03 PM, Ron Johnson wrote:
On 03/01/2018 02:32 PM, David G. Johnston wrote:

There's always the "account number", which is usually synthetic. Credit Card numbers are also synthetic. 

Actually, no:

https://en.wikipedia.org/wiki/Payment_card_number

There is a method to the madness, not just random issuance of numbers. It was made it relatively easy for folks to generate numbers. Hence the addition of CSC codes.

Right.  And how do the issuers generate the individual account identifier within their IIN ranges?


ICD numbers are (relatively)
synthetic, too.

But that doesn't mean we have to use them willy-nilly everywhere.

--
Angular momentum makes the world go 'round.

В списке pgsql-general по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Enforce primary key on every table during dev?
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Enforce primary key on every table during dev?