A model for a historical database is described which is based upon time-stamped tuples as the unit of storage. The model includes both physical and logical time-stamps. The technical characteristics of write-once laser discs prevent the use of double logical time-stamps. The model distinguishes version from correction-updates. It is shown that if setvalued attributes are involved the use of null values is unavoidable if back-dated correction-updates are allowed. A method of handling user-defined integrity constraint rules is outlined which involves the maintenance of a time-stamped trace of such rules. Such a trace is necessary for the proper handling of back-dated correction-updates. An outline of a system SIS-BASE is described which implements someof these ideas.
T. Abbod, K. Brown, H. Noble