Hierarchical data structure is organized into a tree-like structure represented by parent- child relationship. The parent can have many children but each child has only one parent. It is also known as one-to-many relationship. There are many types of data can be represented by hierarchical data structure such as organization structures and programs in academies. In some applications, there is necessary to keep historical data or version that need to be used. Temporal data management is used to handle historical data but cause high data space usage by storing every version data which decrease database efficiency. In this paper, we propose logical design to manage versions of hierarchical data in relational database that that may change overtime but historical data is still needed by reusing duplicated records. This conceptual design can avoid data redundancy and increase database efficiency.
[1]
Christian S. Jensen,et al.
Temporal Entity-RelationshipModels | a Survey
,
1996
.
[2]
Richard T. Snodgrass,et al.
Developing Time-Oriented Database Applications in SQL
,
1999
.
[3]
Jim Melton,et al.
SQL: 1999, formerly known as SQL3
,
1999,
SGMD.
[4]
Randall Weis,et al.
Managing Time in Relational Databases: How to Design, Update and Query Temporal Data
,
2010
.
[5]
Krishna G. Kulkarni,et al.
Temporal features in SQL:2011
,
2012,
SGMD.
[6]
Ralf Hartmut Güting,et al.
Moving Objects Databases
,
2005
.
[7]
Christian S. Jensen,et al.
Temporal Data Management
,
1999,
IEEE Trans. Knowl. Data Eng..
[8]
Bill Karwin,et al.
SQL Antipatterns: Avoiding the Pitfalls of Database Programming
,
2010
.