Transaction Management in Engineering Databases
The assumptions and procedures of engineering design are fundamentally different from those of business applications and result in quite different needs with regard to database system requirements. One important difference is in the assumptions regarding integrity. In business, it is assumed that a database has complete integrity during all quiescent periods. In engineering design, in contrast, integrity does not exist for a database until design is almost complete. In a previous paper, we developed a revised definition of transaction that explicitly allows partial integrity. A management scheme, called entity state transaction management, was proposed that deals with both the partial ordering of transactions and the contention for shared information resources. The extension of this technique for application to large engineering problems is explored in this paper, with the development of a significant example.
KeywordsIntegrity Constraint Concurrency Control Database State Design Database Piping Network
Unable to display preview. Download preview PDF.
- Bernstein, P.A., Shipman, D.W., Wong, W.S. Formal aspects of serializability in database concurrency control. IEEE Trans. Software Eng. SE-5(3), May, 1979.Google Scholar
- Eastman, C.M.Database Facilities for Engineering Design. Proc. IEEE 69(10), Oct., 1981.Google Scholar
- Eastman, C.M., Kutay, A.R. Transactions and Concurrency in Engineering Databases.IBS Report, CMU, 1982.Google Scholar
- Kung, H.T., Papadimitriou, C.H. An optimality theory of concurrency control for databases. CMU Tech. Report, June,1979 (last revised Jan. 1982 ).Google Scholar