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 121bb8e7-7e33-81ff-f0d2-cad4d799595d@cox.net
Whole thread Raw
In response to Re: Enforce primary key on every table during dev?  (Alban Hertroys <haramrae@gmail.com>)
Responses Re: Enforce primary key on every table during dev?  (marcelo <marcelo.nicolet@gmail.com>)
List pgsql-general
Tree view 
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.

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Enforce primary key on every table during dev?
Next
From: Daevor The Devoted
Date:
Subject: Re: Enforce primary key on every table during dev?