[Q] Most logical way to keep history ?

Hi,

What is the most logical solution, or 'best' solution according to database-theory to keep the history of an object (row) in a table.

ie:
Employee Table
Fields: id, Name, Adress, Age

If one changes the Name the old information should be stored somewhere in the database so that the change can be looked up.
(so a history of changes to a certain employee is built up)

Should I make a separate table called 'old employee'. Or use a parent-child kind of relation ship within the Employee Table like: Employee: id, Name, Adress, Age, Parent. where "parent" points to its
(newer) parent. ?

Thanks!

Jerold. Received on Fri Jul 28 2000 - 00:00:00 CEST