Re: Enforce primary key on every table during dev?

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:42:18
Message-ID: 121bb8e7-7e33-81ff-f0d2-cad4d799595d@cox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/01/2018 01:11 PM, marcelo wrote:
>
> On 01/03/2018 16:00 , Ron Johnson 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.
> IMHO, business logic can and must preclude "garbage insertion". Except you
> are inserting data directly to database using SQL, any n-tier architecture
> will be checking data validity.

Any n-tier architecture that's bug-free.

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daevor The Devoted 2018-03-01 20:06:29 Re: Enforce primary key on every table during dev?
Previous Message Ron Johnson 2018-03-01 19:39:10 Re: Enforce primary key on every table during dev?