Message-ID: <51ED3ECB.5020703@dalibo.com>
Date: Mon, 22 Jul 2013 16:16:43 +0200
From: Vik Fearing <vik.fearing@dalibo.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ldrlj1 <russelljanusz@yahoo.com>
CC: pgsql-sql@postgresql.org
Subject: Re: table constraint on two columns
References: <1374501921767-5764645.post@n5.nabble.com>
In-Reply-To: <1374501921767-5764645.post@n5.nabble.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On 07/22/2013 04:05 PM, ldrlj1 wrote:
> Postgres 9.2.4.
>
> I have two columns, approved and comments. Approved is a boolean with no
> default value and comments is a character varying (255) and nullable.
>
> I am trying to create a constraint that will not allow a row to be entered
> if approved is set to false and comments is null.

CHECK constraints work on positives, so restate your condition that
way.  A row is permissible if approved is true or the comments are not
null, correct?  So...

...add constraint chk_comments (approved or comments is not null)...

> This does not work. yada, yada, yada... add constraint "chk_comments' check
> (approved = false and comments is not null). The constraint is successfully
> added, but does not work as I expected.

That's not the same check as what you described.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql