Abstract
Temporal database is an extension of the concept of standard databases which process only current valid data. Temporal structure is not based only on managing historical data, but it should also model the data, the validity of which will be in the future in special structures. This paper deals with the temporal structure on object level in comparison with the column level temporal data. It describes the principles, required methods, procedures, functions and triggers to provide the functionality of this system. It also defines the possible implementations and offers the solution to get the snapshot of the database or the object whenever during the existence. The reason for column level solution development is based on the heterogeneity of the attributes time. Some attributes, however, do not change their values over the time or are updated very rarely, and therefore it is not necessary to record the new values for these attributes.
[1] C.J. Date, Date on Database. Apress, 2006 Search in Google Scholar
[2] C.J. Dat, H. Darwen, N.A. Lorentzos, Temporal data and the relational model (Morgan Kaufmann, 2003) Search in Google Scholar
[3] C.J. Date, Logic and Databases — The Roots of Relational Theory (Trafford Publishing, 2007) Search in Google Scholar
[4] P.N. Hubler, N. Edelweiss, Implementing a Temporal Database on Top of a Conventional Database, 2000, Conference SCCC’ 00, pp. 58–67, 200 Search in Google Scholar
[5] T. Johnson, R. Weis, Managing Time in Relational Databases (Morgan Kaufmann, 2010) Search in Google Scholar
[6] M. Kvet, K. Matiaško, As time flows — in databases, 2013, Conference Informatics 2013, 5.11.–7.11.2013, (Technical University Kosice, 2013) 19–27 Search in Google Scholar
[7] K. Matiaško, M. Vajsová, M. Zábovský, M. Chochlík, Database systems, EDIS, 2008, ISBN: 9788080708207 Search in Google Scholar
[8] Ch.S. Jensen, Introduction to Temporal Database Research, PhD thesis, 2000 Search in Google Scholar
[9] R. Snodgrass, Developing Time-Oriented Database Applications in SQL (Morgan Kaufmann Publishers, San Francisco, 2000) Search in Google Scholar
[10] R. Snodgrass, M. Bohlen, Ch. Jensen, A. Steiner, Adding Transaction Time to SQL/Temporal. ANSI X3H2-96-502r2, 1996 Search in Google Scholar
[11] M. Kvet, A. Lieskovský, K. Matiaško, Temporal data modelling, 2013, IEEE conference ICCSE 2013, 26.4.–28.4.2013, pp. 452–459 Search in Google Scholar
[12] M. Kvet, K. Matiaško, Uni-temporal and Bi-temporal Table, 2013, IEEE conference Digital Technologies 2013, 29.5.–31.5.2013, (EDIS, Zilina, Slovakia, 2013) 43–54 10.1109/DT.2013.6566280Search in Google Scholar
[13] J. Maté, Transformation of Relational Databases to Transaction-Time Temporal Databases, in ECBS-EERC, 27–34, 2011 10.1109/ECBS-EERC.2011.14Search in Google Scholar
[14] M. Kvet, K. Matiaško, Column level uni-temporal, J. Communications, 2013 (in press) Search in Google Scholar
[15] R. Kimball, The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses (John Wiley & Sons, 1996) Search in Google Scholar
[16] M. Kvet, K. Matiaško, Management of Temporal System, Int. J. New Architectures Appl. 3(3), 70–80, 2013 Search in Google Scholar
[17] M. Kvet, K. Matiaško, Uni-temporal Modelling Extension at Object vs. Attribute Level, 2013, IEEE conference EMS 2013, 20.11.–22.1.2013, pp. 7–11 10.1109/EMS.2013.2Search in Google Scholar
© 2014 Versita Warsaw
This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 3.0 License.
