The inverse referential integrity constraints (IRICs) are specialization of
non-key-based inclusion dependencies (INDs). Keybased INDs (referential
integrity constraints) may be fully enforced by most current relational
database management systems (RDBMSs). On the contrary, non-key-based INDs are
completely disregarded by actual RDBMSs, obliging the users to manage them
via custom procedures and/or triggers. In this paper we present an approach
to the automated implementation of IRICs integrated in the SQL Generator tool
that we developed as a part of the IIS
Supporting integrity constraints is essential for database systems. Integrity constraints are used to ensure that the data in a database complies with rules that have been set to establish accurate and acceptable information for a database. Triggers provide a very powerful and flexible means to realize effective constraint enforcing mechanisms. Implementing triggers based on constraint specifications follows some simple rules that are basically independent of a particular commercial database system. This paper gives these rules, which can be used to derive triggers from constraint specifications. A comparison of advantages of constraints and triggers is also given in this paper.
A design specification and a server implementation of the inverse referential integrity constraints
