DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=FGRIMzHasq7lojhfWdrXSK7ixt122K6+3ARk5arnDXjRjOG0b7Klp0SUiKjmqJIrJHWdWzRE2bhhHDiyP8Dq8S8WApue/CQKr1cEHBSmqTqhUKB22rogK6BViUsffVV06nEFeLeRrAElUaTLaSjfWqbxRwptgJAItncbbileYzY=;
Date: Mon, 7 May 2007 07:59:22 -0700 (PDT)
From: Richard Broersma Jr <rabroersma@yahoo.com>
Subject: Temporal Table Relations and Referential Integrity
To: SQL Postgresql List <pgsql-sql@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <124864.59370.qm@web31806.mail.mud.yahoo.com>

In non-temporal tables, changes to the primary key of a Parent table and record deletions can be
cascaded to a related Child table using "REFERENCES Parent( Parent_code ) ON DELETE CASCADE ON
UPDATE CASCADE,"

However, since temporal UPDATEs and DELETEs do not behave in the same way as they do in
non-temporal tables, is anyone able to successfully use Referential Integrity constraints between
Parent and Child tables?  Or are custom triggers the only solution to maintain temporal relations
between Parents and Children?  My question deals specifically with the "Current" style of temporal
relations, where only the currently known attributes and attribute histories are stored.

As a second question, would anyone know if temporal referential integrity is targeted for future
inclusion into the SQL standard?

I would be happy to elaborate on what I mean by Temporal Referential-Integrity (RFI) if my
questions are unclear.

Regards,
Richard Broersma Jr.