This Article 
 Bibliographic References 
 Add to: 
Version Support for Engineering Database Systems
April 1988 (vol. 14 no. 4)
pp. 429-437

In engineering applications, multiple copies of object descriptions have to coexist in a single database. This paper proposes a scheme that enables users to explicitly deal with these object versions. After introducing a basic version model, the problem of "rerouting" interobject references upon the creation of new versions is solved by providing generic references and user-specific environments. Finally, logical version clusters are introduced that allow for the meaningful grouping of versions. The paper concludes with some remarks on implementation and a comparison with other approaches.

[1] M. Adiba and B. Lindsay, "Database snapshots," inProc. 6th hr. Conf. Very Large Databases, 1980, pp. 86-91.
[2] D. S. Batory and A. P. Buchmann, "Molecular objects, abstract data types, and data models: A framework," inProc. 10th Int. Conf. Very Large Databases, 1984, pp. 172-184.
[3] R. Bayer, H. Heller, and A. Reiser, "Parallelism and recovery in database system,"ACM Trans. Database Syst., vol. 5, pp. 139-156, June 1980.
[4] P. Dadam, V. Lum, and H.-D. Werner, "Integration of time versions into a relational database system,"Proc. 10th Int. Conf. Very Large Databases, 1984, pp. 509-522.
[5] R. Haskin and R. Lorie, "On extending the functions of a relational database system, " inProc. ACMSIGMOD, June 1982, pp. 207-212.
[6] M. Haynie, "The relational/network hybrid data model," inProc. 18th Design Automation Conf., 1981, pp. 646-652.
[7] M. Haynie and K. Gohl, "Revision relations-Maintaining revision history information,"Database Eng., vol. 7, pp. 26-34, June 1984.
[8] SQL/Data System. IBM Pmgram Product 5748-XXJ.
[9] W. Kim, et al., "A Transaction Mechanism for Engineering Design Databases,"Proc. Int'l. Conf. Very Large Databases, Morgan Kaufmann, Los Altos, Calif., 1984, pp. 355- 362.
[10] R. H. Katz and T. J. Lehman, "Database support for versions and alternatives of large designfiles," IEEE Trans. Sofware Eng., vol.SE-10, pp. 191-200, Mar. 1984.
[11] H. Kinzinger, "Extension of a database query language to support the version concept,"Informatik-Fachberichte(in German), vol. 72, 1983, pp. 96-112.
[12] P. Klaholdet al., "A transaction model supporting complex applications in integrated information systems," inProc. ACM SIGMOD, 1985, pp. 388-401.
[13] M. R. Klopprogge and P.C. Lockemann, "Modelling information preserving databases: Consequences of the concept of time,"Proc. 9th Int. Conf. Very Large Databases, 1983, pp. 399-416.
[14] R. Lorie,etal., "User interface and access techniques for engineering databases," IBM Res. Lab., San Jose, CA, Res. Rep. RJ4155, 1984.
[15] R. Lorie, and W. Plouffe, "Complex objects and their use in design transactions," inProc. Database Week: Engineering Design Applications (IEEE), 1983, pp. 115-121.
[16] T. Muller and D. Steinbauer, "A language interface for version control in CAM databases,"Informatik-Fachberichte(in German), vol.72, pp. 76-95, 1983.
[17] C. H. Papadimitriou and P. C. Kanellakis, "On concurrency control by multiple versions,"ACM Trans. Database Syst., Mar. 1984.
[18] H.-J. Schekand M. Scholl, "An algebra for the relational model with relation-valued attributes," Technische Hochschule Darmstadt, West Germany, Tech. Rep. DVS I-1984-Tl, 1984.

Index Terms:
Computer-aided design, database, engineering database,object database, versions.
K.R. Dittrich, R.A. Lorie, "Version Support for Engineering Database Systems," IEEE Transactions on Software Engineering, vol. 14, no. 4, pp. 429-437, April 1988, doi:10.1109/32.4664
Usage of this product signifies your acceptance of the Terms of Use.