Received: from gnumed.dhs.org (modem59.malleenet.net.au [203.143.67.123] (may be forged)) by postgresql.org (8.11.3/8.11.4) with SMTP id fAHCthm04862 for ; Sat, 17 Nov 2001 07:55:43 -0500 (EST) (envelope-from hherb@malleenet.net.au) Received: (qmail 6029 invoked by uid 8); 17 Nov 2001 12:55:44 -0000 Message-ID: <20011117125544.6028.qmail@gnumed.dhs.org> Received: from pc-00071.e-smith.gnumed.dhs.org (192.168.1.71, claiming to be "there") by bifrost.e-smith.gnumed.dhs.org with SMTP id smtpdVmmYfs; Sat, 17 Nov 2001 23:55:41 EST Content-Type: text/plain; charset="iso-8859-1" From: Horst Herb To: pgsql-sql@postgresql.org Subject: Re: constraint via selection Date: Sun, 18 Nov 2001 00:00:57 +1100 X-Mailer: KMail [version 1.3.1] References: <20011117121312.5700.qmail@gnumed.dhs.org> In-Reply-To: <20011117121312.5700.qmail@gnumed.dhs.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archive-Number: 200111/251 X-Sequence-Number: 5633 > What would the most efficient formulation of the "check" constraint be > in this case? Sorry, I probably should reformulate my question into "is there a more effficient constraint than a foreign key constraint for this simple problem"? Horst