Skip site navigation (1) Skip section navigation (2)

Re: Referencial integrity when there are timestamp primary keys

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Vilson farias <vilson(dot)farias(at)digitro(dot)com(dot)br>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Referencial integrity when there are timestamp primary keys
Date: 2000-10-10 17:04:56
Message-ID: Pine.BSF.4.10.10010101003190.28197-200000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
This is a stupid garden variety bug and I'm not sure why I didn't catch
it previously.  The patch included is against fairly current sources, but
it may apply cleanly against 7.0.2 as well.

On Fri, 6 Oct 2000, Vilson farias wrote:

> I found a irregular behavior with constraints.
> 
> I can only set a referencial integrity between these tables when there are
> no data, even if there are no change to referential integrity violation.

Attachment: fk2.patch
Description: text/plain (1014 bytes)

In response to

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2000-10-10 17:13:25
Subject: Re: Referencial integrity when there are timestamp primary keys
Previous:From: Tom LaneDate: 2000-10-10 16:12:09
Subject: Re: Pb with arrays in PostgresQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group