pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Broersma Jr <rabroersma@yahoo.com>
To: Michael Glaesemann <grzm@seespotcode.net>
Cc: General Postgresql List <pgsql-sql@postgresql.org>
Subject: Re: Alternative to Select in table check constraint
Date: Fri, 30 Jun 2006 18:41:08 -0700 (PDT)
Message-ID: <20060701014108.79890.qmail@web31811.mail.mud.yahoo.com> (raw)
In-Reply-To: <4FA18A22-AFC2-4C6A-A487-57DAEF09F59F@seespotcode.net>

> >         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)
> 
> CREATE UNIQUE INDEX one_a_badge_per_employee_idx
> ON badges (empno)
> WHERE status = 'A';
> http://www.postgresql.org/docs/8.1/interactive/sql-createindex.html
> http://www.postgresql.org/docs/8.1/interactive/indexes-partial.html

Michael,

Partial indexs seem to be "what the doctor ordered!"   And your suggest is right on, the idea of
the constraint is to allow only one active badge status at a time.

But now that I think about it, using the authors suggestion (if it actually worked), how would
would it be possible to change the active status from one badge to another?

Oh well, partial index are obvious the superior solution since the entire table doesn't not have
to be scanned to determine if the new badge can be set to active.

Once again thanks for the insight.

Regards,

Richard Broersma Jr.



view thread (11+ messages)  latest in thread

Message-ID: <20060701014108.79890.qmail@web31811.mail.mud.yahoo.com>
Permalink:  ../20060701014108.79890.qmail@web31811.mail.mud.yahoo.com/
Also on:    postgresql.org/message-id/20060701014108.79890.qmail@web31811.mail.mud.yahoo.com

 · 

reply

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-sql@postgresql.org
  Cc: rabroersma@yahoo.com, grzm@seespotcode.net
  Subject: Re: Alternative to Select in table check constraint
  In-Reply-To: <20060701014108.79890.qmail@web31811.mail.mud.yahoo.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