From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | "Van Ingen, Lane" <lvaningen(at)ESNCC(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: CHECK Constraints |
Date: | 2005-04-22 16:19:28 |
Message-ID: | 20050422161928.GA50858@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Fri, Apr 22, 2005 at 12:02:41PM -0400, Van Ingen, Lane wrote:
>
> If I were to specify a the following on a field named price in one
> expression, would it succeed?
> CHECK (price = 1 OR price = 2 OR price = 3)
What happened when you tried it? A simple test should answer the
question.
CREATE TABLE foo (
id serial PRIMARY KEY,
price integer NOT NULL CHECK (price = 1 OR price = 2 OR price = 3)
);
INSERT INTO foo (price) VALUES (1);
INSERT 0 1
INSERT INTO foo (price) VALUES (2);
INSERT 0 1
INSERT INTO foo (price) VALUES (3);
INSERT 0 1
INSERT INTO foo (price) VALUES (0);
ERROR: new row for relation "foo" violates check constraint "foo_price_check"
INSERT INTO foo (price) VALUES (4);
ERROR: new row for relation "foo" violates check constraint "foo_price_check"
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2005-04-22 16:37:05 | Re: CHECK Constraints |
Previous Message | Walker, Jed S | 2005-04-22 16:11:00 | Re: Authorized privileges when calling a procedure |