Received: from bjke.com (firewall-user@ganymede.bjke.com [144.210.8.38]) by
	hub.org (8.8.8/8.7.5) with ESMTP id SAA16801 for
	<pgsql-sql@postgreSQL.org>; Fri, 31 Jul 1998 18:56:37 -0400 (EDT)
Received: by bjke.com; id RAA04520; Fri, 31 Jul 1998 17:56:36 -0500 (CDT)
Received: from cpsmail.cpsgroup.com(144.210.12.11) by gauntlet.bjke.com via
	smap (4.1) id xmaa04471; Fri, 31 Jul 98 17:56:13 -0500
Received: by cpsmail with Internet Mail Service (5.0.1458.49)
	id <3XAFWY3A>; Fri, 31 Jul 1998 17:58:23 -0500
Message-ID: <F10BB1FAF801D111829B0060971D839F36DF73@cpsmail>
From: "Jackson, DeJuan" <djackson@cpsgroup.com>
To: Alexey Pushkin <Alexey.Pushkin@fi.uib.no>, postgresql-sql
	<pgsql-sql@postgreSQL.org>
Subject: RE: [SQL] FOREIGN KEY
Date: Fri, 31 Jul 1998 17:58:21 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain

> Hi all.
> 
> As far as I understand PostgreSQL does not support
> FOREIGN KEY syntax. (Do I gather right ?).
Postgres supports the 'syntax' just fine, it simply ignores it.

> What is the recommended work around ?
There is a work-around (triggers) in the contrib directory of the
distribution (refint).  It comes with examples of usage.

> ---
> Alexey Pushkin
> Well Service Technology AS