Re: Why we allow CHECK constraint contradiction?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "Imai, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why we allow CHECK constraint contradiction?
Date: 2018-10-10 05:44:14
Message-ID: CAKFQuwbV-c2qNH1wXD-cDp5gugJw3ickZ7XZbkqxTtTzRY-=FA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday, October 9, 2018, Imai, Yoshikazu <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>
wrote:
>
> Are there any rows which can satisfy the ct's CHECK constraint? If not,
> why we
> allow creating table when check constraint itself is contradicted?
>

I'd bet on it being a combination of complexity and insufficient expected
benefit. Time is better spent elsewhere. Mathmatically proving a
contradiction in software is harder than reasoning about it mentally.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2018-10-10 05:57:42 Re: Why we allow CHECK constraint contradiction?
Previous Message Imai, Yoshikazu 2018-10-10 05:25:27 Why we allow CHECK constraint contradiction?