Databases Reference
In-Depth Information
13
RE-PRESENTING INTERNALIZED
PIPELINE DATASETS
CONTENTS
Internalized Pipeline Datasets
292
Pipeline Datasets as Queryable Objects
296
Posted History: Past Claims About the Past
297
Posted Updates: Past Claims About the Present
298
Posted Projections: Past Claims About the Future
299
Current History: Current Claims About the Past
300
Current Data: Current Claims About the Present
301
Current Projections: Current Claims About the Future
Pending History: Future Claims About the Past
304
Pending Updates: Future Claims About the Present
Pending Projections: Future Claims About the Future
Mirror Images of the Nine-Fold Way
307
The Value of Internalizing Pipeline Datasets
Glossary References
In Chapter 12, we introduced the concept of pipeline datasets.
These are files, tables or other physical datasets in which the
managed object itself represents a type and contains multiple
managed objects each of which represents an instance of that
type, and which in turn themselves contain instances of other
types. Using the language of tables, rows and columns, these
managed objects are tables, the instances they contain are rows,
and those last-mentioned types are the columns of those tables,
whose instances describe the properties and relationships of the
objects represented by those rows.
Because our focus is temporal data management at the level
of tables and rows, and not at the level of databases, we have
discussed pipeline datasets as though there were a distinct set
of them for each production table.
Figure 13.1
shows one con-
ventional table, and a set of eight pipeline datasets related to it.
