A prototype rule-based front end system for integrity enforcement in relational databases: An application to the naval aircraft flight records database

  • Magdi N. Kamel
Integration of Databases and Expert Systems
Part of the Lecture Notes in Computer Science book series (LNCS, volume 856)


An important goal of any database system is to model the real world accurately in a manner consistent with the user's perception of the data. One way to accomplish the accuracy of information in relational databases is through the enforcement of integrity constraints that represent rules pertaining to the organization. Unfortunately most DBMS today do not provide adequate integrity features to ensure the accuracy of data in their databases. This paper discusses the design and implementation of a prototype rule-based front end system for integrity enforcement for the Naval Aircraft Flight Record relational database. The system includes a set of rules that define 1) the update operation that triggers the testing of an integrity rule, 2) a specification of the condition to be tested, and 3) the action to be taken in case of attempted violation. These rules are stored in a knowledge base, which the inference engine of the system uses to enforce database integrity.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Buneman, P. and Clemons, E., “Efficiently Monitoring Relational Databases,” ACM Transactions on Database Systems, Vol. 4, No. 3, Sept. 1979, pp. 368–382.CrossRefGoogle Scholar
  2. [2]
    Codd, E. F., The Relational Model for Database Management, Version 2, Addison-Wesley Publishing Co., Inc., 1990.Google Scholar
  3. [3]
    Date, C. J., An Introduction to Database Systems, Vol. 1, Fourth Edition, Addison-Wesley Publishing Co., Inc., 1986.Google Scholar
  4. [4]
    Date, C. J., “Referential Integrity,” Proc. 7th International Conference on Very Large Data Bases, September 1981.Google Scholar
  5. [5]
    Eswaren, K. P., “Specifications, Implementations and Interactions of a Trigger Subsystem in an Integrated Database System,” IBM Research Report RJ1820, San Jose, CA, November 1976.Google Scholar
  6. [6]
    Department of the Navy, Office of the Chief of Naval Operation, “OPNAVINST 3710.7N,” Natops General Flight and Operating Instructions, April 1990.Google Scholar
  7. [7]
    Fernandez, E. B., Summers, R. C., and Wood, C., Database Security and Integrity, Addison-Wesley Publishing Co., Inc., 1986.Google Scholar
  8. [8]
    Stonebraker, M., “The Integration of Rule Systems and Database Systems,” IEEE Transactions on Knowledge and Data Engineering, Vol. 4, No. 5, October 1992, pp. 415–423.Google Scholar
  9. [9]
    Stonebraker, M., “Adding Semantic Knowledge to a Relational Database System,” In On Conceptual Modeling, Brodie, M. L., Mylopoulos, J., and Schmidt, J. W. (Eds.), New York, NY: Springer-Verlag, 1984. pp. 334–353.Google Scholar
  10. [10]
    Stonebraker, M., “Implementation of Integrity Constraints and Views by Query Modification,” Proc. 1975 ACM SIGMOD International Conference on the Management of Data. San Jose, CA, 1975, pp. 65–68.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1994

Authors and Affiliations

  • Magdi N. Kamel
    • 1
  1. 1.Information Systems GroupNaval Postgraduate SchoolMontereyUSA

Personalised recommendations