The attribute-oriented approach
An object-level temporal solution is a relevant solution if the changes are synchronized and occur simultaneously. Thus, frequency, as well as the completeness of the change, must inevitably be synchronized too. Otherwise, duplicate values will be present, resulting in performance degradation and rising disc storage costs. This is caused by the primary key extension dealing with the time elements expressing various characteristics, mostly related to the validity frame. The opposite of object-level temporal granularity is associated with the attribute itself. Therefore, each attribute is treated separately, providing robustness with an emphasis on the different granularity and frequency of the changes. As a result, a particular system can cover any attribute in the core table:
- Static attributes are not changed at all. Once they are initialized, there is no possibility of change. The existing set can be extended by adding new elements (if approved...
