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-01T19:39:10Z
Lists: pgsql-general
On 03/01/2018 01:05 PM, Melvin Davidson wrote:
>
>
> On Thu, Mar 1, 2018 at 2:00 PM, Ron Johnson <ron.l.johnson@cox.net 
> <mailto:ron.l.johnson@cox.net>> wrote:
>
>     On 03/01/2018 12:32 PM, Daevor The Devoted wrote:
>
[snip]
>
>>     If your only unique index is a synthetic key, then you can insert the
>>     same "business data" multiple times with different synthetic keys.
>
>
>     -- 
>     Angular momentum makes the world go 'round.
>
>
> *If you are going to go to the trouble of having a surrogate/synthetic 
> key, then you may as well have a primary key , which is much better. *

I completely agree.

-- 
Angular momentum makes the world go 'round.