Re: Temporal database - no end date
From: Frank Hamersley <terabitemightbe_at_bigpond.com>
Date: Tue, 23 Jan 2007 12:40:02 GMT
Message-ID: <Cmnth.5207$u8.3751_at_news-server.bigpond.net.au>
Date: Tue, 23 Jan 2007 12:40:02 GMT
Message-ID: <Cmnth.5207$u8.3751_at_news-server.bigpond.net.au>
Kev wrote:
[..]
> As I started the thread in search of some particular information, I
> would like to thank Celko for providing a clear explanation to my
> problem. I can now see that having two dates makes each row a complete
> fact and thus avoiding joins/correlated queries.
Just be aware this is not a "silver bullet" solution...for all the papers published the concept of how to "properly" integrate time into the RM (or even SQL) has not been pulled off to the level that it has been accepted into the standards, vendors, industry or as discovered this NG.
Cheers, Frank. Received on Tue Jan 23 2007 - 13:40:02 CET