| From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Enforce primary key on every table during dev? |
| Date: | 2018-03-01 19:39:10 |
| Message-ID: | b8800ed8-d0dc-2965-0cc7-d60fcb3d459c@cox.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(dot)l(dot)johnson(at)cox(dot)net
> <mailto:ron(dot)l(dot)johnson(at)cox(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2018-03-01 19:42:18 | Re: Enforce primary key on every table during dev? |
| Previous Message | marcelo | 2018-03-01 19:11:09 | Re: Enforce primary key on every table during dev? |