Re: complex referential integrity constraints - Mailing list pgsql-general

From Joris Dobbelsteen
Subject Re: complex referential integrity constraints
Date
Msg-id 73427AD314CC364C8DF0FFF9C4D693FF5585@nehemiah.joris2k.local
Whole thread Raw
In response to complex referential integrity constraints  ("Robert Haas" <Robert.Haas@dyntek.com>)
Responses Re: complex referential integrity constraints  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Re: complex referential integrity constraints  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
>-----Original Message-----
>From: pgsql-general-owner@postgresql.org
>[mailto:pgsql-general-owner@postgresql.org] On Behalf Of
>Martijn van Oosterhout
>Sent: donderdag 22 februari 2007 18:17
>To: Joris Dobbelsteen
>Cc: Robert Haas; pgsql-general@postgresql.org
>Subject: Re: [GENERAL] complex referential integrity constraints
>
>On Thu, Feb 22, 2007 at 05:28:35PM +0100, Joris Dobbelsteen wrote:
>> Even worse, I don't you can guarentee that this constraint
>is enforced
>> at all times. That means, not if you are using triggers.
>> The only option seems using foreign keys and put in a lot of
>redundant
>> data.
>
>Err, foreign keys are implemented using triggers, so this
>statement is self-contradictary.

Are you really sure they are executed under the same visibility rules?

- Joris

pgsql-general by date:

Previous
From: "Chad Wagner"
Date:
Subject: Re: postgresql vs mysql
Next
From: Tomas Simonaitis
Date:
Subject: Moving WAL files