From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
Cc: | General Postgresql List <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Alternative to Select in table check constraint |
Date: | 2006-07-01 00:27:07 |
Message-ID: | 4FA18A22-AFC2-4C6A-A487-57DAEF09F59F@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Jul 1, 2006, at 6:55 , Richard Broersma Jr wrote:
> CHECK ( 1 = ALL ( SELECT COUNT(STATUS)
> FROM BADGES
> WHERE STATUS = 'A'
> GROUP BY EMPNO))
From the PostgreSQL docs (http://www.postgresql.org/docs/8.1/
interactive/sql-createtable.html)
> Currently, CHECK expressions cannot contain subqueries nor refer to
> variables other than columns of the current row.
This is why the the above won't work. You can probably do something
similar by creating UNIQUE index with a WHERE clause. For example (if
I'm understanding the intent),
CREATE UNIQUE INDEX one_a_badge_per_employee_idx
ON badges (empno)
WHERE status = 'A';
Here are links to more documentation on indexes:
http://www.postgresql.org/docs/8.1/interactive/sql-createindex.html
http://www.postgresql.org/docs/8.1/interactive/indexes-partial.html
Hope this helps.
Michael Glaesemann
grzm seespotcode net
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma Jr | 2006-07-01 01:41:08 | Re: Alternative to Select in table check constraint |
Previous Message | Richard Broersma Jr | 2006-06-30 22:49:36 | Re: How To Exclude True Values |