Re: Check constraints do not seem to be working!!! - Mailing list pgsql-general

From Jitendra Loyal
Subject Re: Check constraints do not seem to be working!!!
Date
Msg-id CAGBkuscy+YehMzqAmhijQrQ37yhDAMSaWQ+rJJMmA1zWN_3ZaA@mail.gmail.com
Whole thread Raw
In response to Re: Check constraints do not seem to be working!!!  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
Responses Re: Check constraints do not seem to be working!!!  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Re: Check constraints do not seem to be working!!!  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general
Thanks Nikolay

I read that but is there a way to meet the above requirement. And I will like to add that IS NULL and IS NOT NULL should evaluate to true/false. These operators are made for this and should not be returning NULL.

Regards,
Jitendra

On Wed 11 Nov, 2020, 14:18 Nikolay Samokhvalov, <samokhvalov@gmail.com> wrote:
On Wed, Nov 11, 2020 at 12:26 AM Jitendra Loyal <jitendra.loyal@gmail.com> wrote:
Despite the above two constraints, the following rows get into the table:
     insert into t (b , c) values (null, true), (null, false);  


> It should be noted that a check constraint is satisfied if the check expression evaluates to true or the null value. Since most expressions will evaluate to the null value if any operand is null, they will not prevent null values in the constrained columns. To ensure that a column does not contain null values, the not-null constraint described in the next section can be used.

pgsql-general by date:

Previous
From: Nikolay Samokhvalov
Date:
Subject: Re: Check constraints do not seem to be working!!!
Next
From: RAJAMOHAN
Date:
Subject: Need to place pgpool logs on separate directory