Received: from garbo.DK.net (garbo.DK.net [193.88.44.23])
	by hub.org (8.9.1/8.9.1) with ESMTP id IAA22699
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 4 Jan 1999 08:41:01 -0500 (EST) (envelope-from leif@danmos.dk)
From: leif@danmos.dk
Received: (from uucp@localhost) by garbo.DK.net (8.8.8/8.8.8) id OAA05560 for
	postgreSQL.org!pgsql-interfaces; Mon, 4 Jan 1999 14:40:54 +0100 (MET)
>Received: from danmos.dk by danmos with smtp
	(Smail3.1.28.1 #64) id m0zxADW-000G4UC; Mon, 4 Jan 99 14:38 MET
Message-Id: <m0zxADW-000G4UC@danmos>
Date: Mon, 4 Jan 99 14:24 WST
To: pgsql-interfaces@postgreSQL.org
Subject: How to implement referential facilities in PostgreSQL
Content-Type: text


    Hi everybody,

     Happy New Year to you all.


   We have a rather large M$ Access application for time and attendance
and job time registration. It has been implemented in M$ Access using a
M$ Access database running on a M$ 'operating system'.

   One of our issues is to use the PostgreSQL in stead of/underneath the
M$ Access database application, which is the existing application running
well on M$ Access with not so large amounts of data. We of course need
to run this on a Linux box. The application makes extensive use of some
Access 'referential features'.

   So my question is:

   What is the equivalent of

     'Enforce Referential Integrity',
     'Cascade Update Related Fields', and
     'Cascade Update Related Records' in

SQL/PostgreSQL terms. In other words, how do I get these facilities into
my PostgreSQL database? I need to be able to have the M$ Access application
to link directly to the PostgreSQL tables using ODBC, which I have managed
to copy directly using Access, but with no Primary/Foreign keys what so ever.


   Thanks for any sugestions,

  Leif