Received: from tsai3.teleline.es (teleline.teleline.es [194.224.53.3]) by hub.org (8.8.8/8.7.5) with ESMTP id KAA22509 for ; Tue, 23 Jun 1998 10:15:48 -0400 (EDT) Received: from default ([195.235.10.185]) by tsai3.teleline.es (Netscape Mail Server v2.02) with SMTP id AAA15132 for ; Tue, 23 Jun 1998 16:27:41 +0200 Message-ID: <001c01bd9eb1$6a136d60$b90aebc3@default> From: "Dionisio Barrantes Blanco" To: "soporte postgres ingles" Subject: foreign keys Date: Tue, 23 Jun 1998 16:15:44 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01BD9EC2.2CC20A00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 This is a multi-part message in MIME format. ------=_NextPart_000_0019_01BD9EC2.2CC20A00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Somebody can tell me how Postgres solves the referential integrity = problem. I think I can't use 'constraints' for foreign keys. =BFWhat's = the easier way to declare and manage foreign keys? . Thanks Dionisio Barrantes ------=_NextPart_000_0019_01BD9EC2.2CC20A00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Somebody can tell me how Postgres = solves the=20 referential integrity problem. I think I can't use 'constraints'  = for=20 foreign keys. ¿What's the easier way to declare and manage = foreign keys?=20 .
 
Thanks
Dionisio Barrantes
------=_NextPart_000_0019_01BD9EC2.2CC20A00--