From: Gnanakumar <gnanam@zoniac.com>
To: pgsql-admin@postgresql.org
Subject: Is it possible to create a CHECK constraint for my use case?
Date: Tue, 31 Jan 2012 13:41:00 +0530
Message-ID: <006c01ccdfef$e0396f60$a0ac4e20$@com> (raw)
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?
Regards,
Gnanam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gnanam@zoniac.com
Subject: Re: Is it possible to create a CHECK constraint for my use case?
In-Reply-To: <006c01ccdfef$e0396f60$a0ac4e20$@com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox