| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Enforce primary key on every table during dev? |
| Date: | 2018-03-01 21:14:38 |
| Message-ID: | ed7d8c78-d0ef-c895-e0a4-3f3459a1670e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
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.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-03-01 21:21:41 | Re: Enforce primary key on every table during dev? |
| Previous Message | Tim Cross | 2018-03-01 21:06:42 | Re: Enforce primary key on every table during dev? |