From: Richard Broersma Jr <rabroersma@yahoo.com>
To: SQL Postgresql List <pgsql-sql@postgresql.org>
Subject: Temporal Table Relations and Referential Integrity
Date: Mon, 7 May 2007 07:59:22 -0700 (PDT)
Message-ID: <124864.59370.qm@web31806.mail.mud.yahoo.com> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: rabroersma@yahoo.com
Subject: Re: Temporal Table Relations and Referential Integrity
In-Reply-To: <124864.59370.qm@web31806.mail.mud.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox