Postgres Pro
Downloads
Home   >   mailing lists

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

From Ron Johnson
Subject Re: Enforce primary key on every table during dev?
Date
Msg-id b8800ed8-d0dc-2965-0cc7-d60fcb3d459c@cox.net
Whole thread Raw
In response to Re: Enforce primary key on every table during dev?  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general
Tree view
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> 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.

pgsql-general by date:

Previous
From: marcelo
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?