Re: Temporal database

From: <marcpark_at_my-deja.com>
Date: 2000/04/28
Message-ID: <8ecthn$nvs$1@nnrp1.deja.com>#1/1

There are several things you can do to have your model have history. You can have an active_cd = 1 for active and 0 for inactive. You can have a replace_dt for items that have been replaced, etc. You can have a 2nd table for history, etc.

You best know what your model does, and what the impact of having the history data in the tables. It seems to me the simplest solution is to have a established date and a replaced date for the items in your table. When you update an item, set the replaced to = sysdate (or the like) and set the new established date = sysdate + 1 (Or the like) then your tables will contain history. You may also need to use the established date in the primary key.

Marc G. Parkinson

In article <3909B420.DBC7626C_at_ubs.com>,
juerg fuchs <juerg.fuchs_at_ubs.com> wrote:
>
> --------------BDF87A9036A8173E5204CD1F
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Hello
>
> I'm designing a data model for configuration data. Since some of the
> configuration data doesn't have a version and this configuration data
> changes over the time, I need to historize the data. The data model
> without the historziation model is very big and complex.
>
> Example:
>
> SCHED_NBR SCHED_ID SCHED_TYPE BEGIN_TIME_STAMP
> END_TIME_STAMP
> ------------------- --------------- --------------------
> ------------------------------ -------------------------
> 1 s1 Stype1
> 04/01/00 04/03/00
> 1 s1 Stype2
> 04/03/00
>
> SCHED_TYPE=f(BEGIN_TIME_STAMP)
>
> Questions:
>
> 1.) Is there existing functionality to implement the historisation of
> data.
> 2.) Does anybody have experience in implementing a temporal database
or
> knows publications about this topic.
>
> Cheers
>
> Juerg Fuchs
>
> --------------BDF87A9036A8173E5204CD1F
> Content-Type: text/html; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
> <html>
> Hello
> I'm designing a data model for configuration data. Since some of
the
> configuration data doesn't have a version and this configuration data
changes
> over the time, I need to historize the data. The data model without
the
> historziation model is very big and complex.
> Example:
> SCHED_NBR    SCHED_ID   
SCHED_TYPE   
> BEGIN_TIME_STAMP    END_TIME_STAMP
> -------------------  ---------------  

 --------------------&nbsp;&nbsp;


> ------------------------------&nbsp;&nbsp;&nbsp;

 -------------------------

>

 1           & nbsp;           & nbsp;
>

s1           &nbs p;      
>

Stype1                  
>

04/01/00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;

> 04/03/00 
>

1           &nbsp ;           &nbsp ;
>

s1           &nbs p;      
>

Stype2                  
> 04/03/00
> SCHED_TYPE=f(BEGIN_TIME_STAMP)
>  
> Questions:
> 1.) Is there existing functionality to implement the historisation
of
> data.
> 2.) Does anybody have experience in implementing a temporal
database
> or knows publications about this topic.
>  
> Cheers
> Juerg Fuchs
>  
>  
>  
>  
>  
>  
>  
>  
>  </html>
>
> --------------BDF87A9036A8173E5204CD1F--
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Apr 28 2000 - 00:00:00 CDT