Search Postgresql Archives

Re: Enforce primary key on every table during dev?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/01/2018 01:05 PM, Melvin Davidson wrote:


On Thu, Mar 1, 2018 at 2:00 PM, Ron Johnson <ron.l.johnson@xxxxxxx> 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.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux