| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tim Cross <theophilusx(at)gmail(dot)com> |
| Cc: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Enforce primary key on every table during dev? |
| Date: | 2018-03-01 21:21:41 |
| Message-ID: | CAKFQuwYkVTVmLgtJbC0nDqcPAO5K2T4zMQ6-05VOeqgWP5yR9w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 1, 2018 at 2:06 PM, Tim Cross <theophilusx(at)gmail(dot)com> wrote:
> +1. And a good test of your underlying data model is whether you can
> identify a natural primary key. If you can't, chances are your model is
> immature/flawed and needs more analysis.
>
https://en.wikipedia.org/wiki/All_models_are_wrong
Unfortunately identifying a natural primary key doesn't guarantee that
one's model is mature, unblemished, and complete - the model writer may
just not know what they don't know. But they may know enough, or the
application is constrained enough, for it to be useful anyway.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2018-03-01 21:26:55 | Re: Enforce primary key on every table during dev? |
| Previous Message | Adrian Klaver | 2018-03-01 21:14:38 | Re: Enforce primary key on every table during dev? |