🚀 go-pugleaf

I am facing a design problem that I hope the Gurus here can assist ...

I am maintain the database of an equipment, including details of its 
various parts, and colour  ....
Through the life span of the equipment, the parts are changed, colour 
replaced.

What is the best way to keep track of the changes?
This is required so that questions such as these can be answered ..

1. Which equipments have undergone a colour change from RED TO BLUE?
2. How many equipments have had part A replaced within the last 5 years?
   etc etc ..
3. What is amount spend for replacing part for a particular equipment?

In mosty situation, there are two ways to handle the equipment details.

If history of changes are of no consequence,
One way is to handle keep all the information in one single file and 
changes are made directly on to it.  (A parallel case would be Customer 
details ...and details are keyed directly into it) But then how to track 
the changes in this case?

The otherway is to have an assembly type of database in which the 
compnent are kept .. (how then to keep information on non-component such 
as Colour).  In this case History can be created vai a transaction file 
to report the changes.

Have any one here face similar problem and how you resolve this?

Please note that I am not talking about audit trail here, but history file.


I look forward to an interesting discussion and exposition to this 


Foo Sayhow