Re: History tracking in databases
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@email.mot.com wrote in article <872763022.5320@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"><p><font size=3D2 = color=3D"#000000" face=3D"Times New Roman">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.<br><br>COLIN.<br><br><br><br><font = color=3D"#0000FF"><u>bhq001@email.mot.com</u><font color=3D"#000000"> = wrote in article <<font = color=3D"#0000FF"><u>872763022.5320@dejanews.com</u><font = color=3D"#000000">>...<br>> Hi,<br>> <br>> I am trying to = develop a relational database for a<br>> project at work.<br>> = Currently we are at the logical design phase for<br>> this = database.<br>> The database structure is very hierarchical due = to<br>> the data requirements<br>> of the project.<br>> As part = of the design requirements, the database<br>> must provide means = of<br>> tracking historical data. This is further explained<br>> = below:<br>> <br>> Say you have a CRATE (CRATE1) which can = contain<br>> smaller BOXes (BOX1,BOX2<br>> etc.)<br>> <br>> = CRATE1 is related to BOX1 and BOX2.<br>> <br>> Each BOX contains = information specific to itself.<br>> <br>> Say BOX1 information = was changed for some reason but<br>> we would still like<br>> to = know the previous information for BOX1.<br>> <br>> CRATE1 is now = related to BOX1,BOX1(old),BOX2<br>> <br>> Question: How would this = kind of relationship be<br>> implemented in an RDBMS?<br>> = <br>> Thanks in advance for any advice given.<br>> <br>> = H.Quan<br>> <br>> -------------------=3D=3D=3D=3D Posted via Deja = News =3D=3D=3D=3D-----------------------<br>> = <font = color=3D"#0000FF"><u>http://www.dejanews.com/</u><font = color=3D"#000000"> Search, Read, Post to = Usenet<br>> </p> </font></font></font></font></font></font></font></body></html> ------=_NextPart_000_01BCB649.B92663E0--