Postgres Pro
Downloads
Home   >   mailing lists

Re: Enforce primary key on every table during dev? - Mailing list pgsql-general

From David G. Johnston
Subject Re: Enforce primary key on every table during dev?
Date
Msg-id CAKFQuwYkVTVmLgtJbC0nDqcPAO5K2T4zMQ6-05VOeqgWP5yR9w@mail.gmail.com
Whole thread Raw
In response to Re: Enforce primary key on every table during dev?  (Tim Cross <theophilusx@gmail.com>)
List pgsql-general
Tree view
On Thu, Mar 1, 2018 at 2:06 PM, Tim Cross <theophilusx@gmail.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.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Enforce primary key on every table during dev?
Next
From: Ron Johnson
Date:
Subject: Re: Enforce primary key on every table during dev?