| From: | marcelo <marcelo(dot)nicolet(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Enforce primary key on every table during dev? |
| Date: | 2018-03-01 20:08:57 |
| Message-ID: | e3375c58-189d-4db0-c25c-8743d22819a4@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/03/2018 16:42 , Ron Johnson wrote:
> 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.
>
Do you know about unit testing?
---
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daevor The Devoted | 2018-03-01 20:09:30 | Re: Enforce primary key on every table during dev? |
| Previous Message | Daevor The Devoted | 2018-03-01 20:06:29 | Re: Enforce primary key on every table during dev? |