Re: Enforce primary key on every table during dev?

Ron Johnson <ron.l.johnson@cox.net>

From: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql-general@lists.postgresql.org
Date: 2018-03-01T21:26:55Z
Lists: 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.