From: | erwan ancel <erwan(dot)ancel(at)free(dot)fr> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | PostgreSQL-general <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: check constraint |
Date: | 2003-06-02 14:00:43 |
Message-ID: | 1054562442.6379.12.camel@brisedorient |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
well, no... these are not direct foreign keys. The constraint here is
that for a given record of D, B pointed by A pointed by the given D must
be the same as B pointed by C pointed by the given D.
This is not a foreign key, or foreign keys are much more than what I
thought.
Erwan
Le lun 02/06/2003 à 15:08, Bruno Wolff III a écrit :
> On Mon, Jun 02, 2003 at 10:52:00 +0200,
> erwan ancel <erwan(dot)ancel(at)free(dot)fr> wrote:
> > Hi,
> > I would like to know if it is possible to set "complex" constraints on
> > databases such as:
> >
> > A->B means that in table A, each record references a record of table B
> > (or NULL)
> >
> > so we have:
> >
> > A->B
> > C->B
> > D->C
> > D->A
> > constraint: for one record of D, D->A->B = D->C->B
> >
> > Hope it is clear enough.
>
> It looks like you are talking about foreign keys. Postgres has foreign key
> constraints. You can look at the create table documentation to see how
> to define them when creating a table.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-06-02 14:02:22 | Re: ERROR: CreateTrigger: function..... |
Previous Message | Ian Harding | 2003-06-02 13:57:18 | Re: implicit abort harmful? |