Re: Check constraint problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Michael Schmidt" <MichaelMSchmidt(at)msn(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Check constraint problem
Date: 2005-07-01 03:30:33
Message-ID: 24187.1120188633@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Michael Schmidt" <MichaelMSchmidt(at)msn(dot)com> writes:
> ALTER TABLE "ClinData" ADD CONSTRAINT "Control_Score" CHECK
> ((("Control_Score_M" IS NULL) AND ("Control_Score_SD" IS NULL) ) OR
> (("Control_Score_M" IS NOT NULL) AND ("Control_Score_SD" >= 0.0)))

> This statement executes okay. It prevents Control_Score_M of NULL and
> Control_Score_SD = 1.0 (as it should). However, it allows
> Control_Score_M = 1 and Control_Score_SD of NULL (it shouldn't). Any
> thoughts about what is wrong. Thanks!

The check constraint evaluates to NULL, which per SQL spec is not a
failure condition (this is different from the behavior of NULL in WHERE).
You need to add an explicit "Control_Score_SD IS NOT NULL" to the second
part of the constraint. As is, for values of 1 and NULL you get

(false AND true) OR (true AND null)
ie
false OR null
ie
null

(remember null effectively means "unknown" in SQL's 3-state boolean
logic)

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marc G. Fournier 2005-07-01 03:33:55 Re: [ANNOUNCE] Language to use with SQL database - Number ONE computer
Previous Message Michael Schmidt 2005-07-01 03:04:36 Check constraint problem