Re: History tracking in databases

From: Colin Robinson <Colin_Robinson_at_msn.com>
Date: 1997/08/31
Message-ID: <01bcb641$5761fbe0$a44e95c1@colin>#1/1

This is a multi-part message in MIME format.

------=_NextPart_000_01BCB649.B92663E0
Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Cant you implement this with 3 stages cases,components,transactions with transactions related to boxes and date/time stamped in desending order showing only top 3 transactions by default.

COLIN. bhq001_at_email.mot.com wrote in article <872763022.5320_at_dejanews.com>...
> Hi,
>
> I am trying to develop a relational database for a
> project at work.
> Currently we are at the logical design phase for
> this database.
> The database structure is very hierarchical due to
> the data requirements
> of the project.
> As part of the design requirements, the database
> must provide means of
> tracking historical data. This is further explained
> below:
>
> Say you have a CRATE (CRATE1) which can contain
> smaller BOXes (BOX1,BOX2
> etc.)
>
> CRATE1 is related to BOX1 and BOX2.
>
> Each BOX contains information specific to itself.
>
> Say BOX1 information was changed for some reason but
> we would still like
> to know the previous information for BOX1.
>
> CRATE1 is now related to BOX1,BOX1(old),BOX2
>
> Question: How would this kind of relationship be
> implemented in an RDBMS?
>
> Thanks in advance for any advice given.
>
> H.Quan
>
> -------------------==== Posted via Deja News ====-----------------------
> http://www.dejanews.com/ Search, Read, Post to Usenet
>

------=_NextPart_000_01BCB649.B92663E0
Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

<html><head></head><BODY bgcolor=3D"#FFFFFF">Cant you implement this with = 3 stages cases,components,transactions with transactions related to = boxes and date/time stamped in desending order showing only top 3 = transactions by default. COLIN. bhq001_at_email.mot.com = wrote in article <872763022.5320_at_dejanews.com>... > Hi, > > I am trying to = develop a relational database for a > project at work. > = Currently we are at the logical design phase for > this = database. > The database structure is very hierarchical due = to > the data requirements > of the project. > As part = of the design requirements, the database > must provide means = of > tracking historical data. This is further explained > = below: > > Say you have a CRATE (CRATE1) which can = contain > smaller BOXes (BOX1,BOX2 > etc.) > > = CRATE1 is related to BOX1 and BOX2. > > Each BOX contains = information specific to itself. > > Say BOX1 information = was changed for some reason but > we would still like > to = know the previous information for BOX1. > > CRATE1 is now = related to BOX1,BOX1(old),BOX2 > > Question: How would this = kind of relationship be > implemented in an RDBMS? > = > Thanks in advance for any advice given. > > =

H.Quan<br>&gt; <br>&gt; -------------------=3D=3D=3D=3D Posted via Deja =
News =3D=3D=3D=3D-----------------------<br>&gt; =

http://www.dejanews.com/     Search, Read, Post to = Usenet > 
</body></html> ------=_NextPart_000_01BCB649.B92663E0-- Received on Sun Aug 31 1997 - 00:00:00 CDT