Transaction management in design databases
Databases are being increasing applied to support design and engineering, implemented on a backend file server and supporting shared access. A fundamental difference between traditional database management and design database management is that for most of the design process, integrity is partial. A management scheme, called entity state transaction management, is proposed that deals with both the partial ordering of transactions and concurrency control over shared information resources. The techniques for automatic management of integrity are described in the light of the following problems: coordinating iterated partial analyses of an engineering system, propagation of design decisions in one subsystem to other subsystems and concurrent design operations within a single subsystem. The implications of entity state management for engineering database schema definition are also explored.
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), October, 1981.Google Scholar
- Eastman, C.M., Kutay, A.R. Transactions and Concurrency in Engineering Databases. IBS Report, CMU, 1982.Google Scholar
- Eswaren, K.P., Gray, J.N., Lorie, R.A., Traiger, I.L. The notions of consistency and predicate locks in a shared database system. Communications ACM 19(2): 624–633, Nov., 1976.Google Scholar
- Gray, J. Notes on Database Operating Systems. Operating Systems — An Advanced Course. Springer Verlag, 1978.Google Scholar
- Kung, H.T. and J.T. Robinson On optimistic methods of concurrency control. ACM Transaction Database Systems 6,2 (June 1981), 213–226.Google Scholar
- Moss, J. Eliot Nested Transactions: An Approach to Reliable Distributed Computing. MIT Press, 1985.Google Scholar