Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.astraweb.com!news-small.astraweb.com!newsfeed.news2me.com!elnk-nf2-pas!newsfeed.earthlink.net!newshub.sdsu.edu!headwall.stanford.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: googlegroups@jayritchie.com (Jay)
Newsgroups: comp.databases.theory
Subject: ERD for time-based relationships
Date: 8 Aug 2003 11:03:50 -0700
Organization: http://groups.google.com/
Lines: 14
Message-ID: <dccfa262.0308081003.73c0a954@posting.google.com>
NNTP-Posting-Host: 65.171.226.140
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1060365831 12025 127.0.0.1 (8 Aug 2003 18:03:51 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 8 Aug 2003 18:03:51 GMT
Xref: newssvr20.news.prodigy.com comp.databases.theory:20823

I'd like to know if anyone can recommend how to best persist
relationships between 2 entities that only exist for a period of time.
For example, there is a relationship between a master account and a
sub-account. I want to know for any date, what the sub-accounts exist
for a specific master account.

Other requirements:
-Prefer a design that can persist a relationship between any 2
entities, i.e., one relationship table for all relationships in a db.
-Enforce multiplicity constraints

Thanks.

Jay A. Ritchie