To: pgsql-admin@postgresql.org
From: Walter Hurry <walterhurry@lavabit.com>
Subject: Re: Is it possible to create a CHECK constraint for my use case?
Date: Wed, 1 Feb 2012 01:04:58 +0000 (UTC)
Lines: 28
Message-ID: <jga33q$vpb$1@dough.gmane.org>
References: <006c01ccdfef$e0396f60$a0ac4e20$@com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT
	30dc37b master)

On Tue, 31 Jan 2012 13:41:00 +0530, Gnanakumar wrote:

> Hi,
> 
> Our Production server is running PostgreSQL v8.2.22 on CentOS5.2.  We
> want to enable a specific CHECK constraint for our application table as
> explained below:
> 
> There are 2 columns in the table: "managertype" numeric(1) and
> "managerid" numeric(10).  "managertype" accepts only 2 valid values,
> either '1' or '2'.
> 
> managertype  |	managerid ---------------------------------
>         1           |  null values NOT allowed 2           | null values
>         allowed
> ---------------------------------
> 
> We want to enable a CHECK constraint based on 2 columns data in the
> table in such a way that if "managertype" is 1, then null values are not
> allowed in "managerid" column.  In other words, I want to create a CHECK
> constraint something like this: IF (managertype = 1) THEN managerid IS
> NOT NULL.
> 
> Is it possible to create a CHECK constraint for my use case explained
> above?

Production server? Bollocks. It's homework. Look it up.