[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-sql
Subject:    [SQL] Alternative to Select in table check constraint
From:       Richard Broersma Jr <rabroersma () yahoo ! com>
Date:       2006-06-30 21:55:12
Message-ID: 20060630215512.18287.qmail () web31813 ! mail ! mud ! yahoo ! com
[Download RAW message or body]

I am practicing with SQL examples comming from the book:

JOE CELKO'S
SQL
PUZZLES
& ANSWERS

The following codes doesn't work on PostgreSQL 8.1.4 but according to the book does conform to
SQL-92.  Is there any other solutions that would result in the same effect?  Or is this an example
of a contraint that should be avoided at all costs?

CREATE TABLE BADGES
(
        BADGENO         SERIAL NOT NULL PRIMARY KEY,
        EMPNO           INTEGER NOT NULL REFERENCES SECEMPLOYEES (EMPNO),
        ISSUEDATE       DATE NOT NULL,
        STATUS          CHAR(1) NOT NULL CHECK ( STATUS IN ('A', 'I')),

        CHECK   ( 1 = ALL (     SELECT COUNT(STATUS)
                                FROM BADGES
                                WHERE STATUS = 'A'
                                GROUP BY EMPNO))
);


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org
[prev in list] [next in list] [prev in thread] [next in thread]