A theorem-proving approach to database integrity
Foundations of deductive databases and logic programming
Heuristics for syntactial optimization of relational queries
Information Processing Letters
Safety and translation of relational calculus
ACM Transactions on Database Systems (TODS)
Constraint checking with partial information
PODS '94 Proceedings of the thirteenth ACM SIGACT-SIGMOD-SIGART symposium on Principles of database systems
Materialized view maintenance and integrity constraint checking: trading space for time
SIGMOD '96 Proceedings of the 1996 ACM SIGMOD international conference on Management of data
Independence of logic database queries and update
PODS '90 Proceedings of the ninth ACM SIGACT-SIGMOD-SIGART symposium on Principles of database systems
Comparing and Synthesizing Integrity Checking Methods for Deductive Databases
Proceedings of the Tenth International Conference on Data Engineering
Drawing Updates From Derivations
ICDT '90 Proceedings of the Third International Conference on Database Theory
The Range Form of Databases and Queries or: How to Avoid Floundering
5. Österreichische Artificial Intelligence-Tagung
Queries Independent of Updates
VLDB '93 Proceedings of the 19th International Conference on Very Large Data Bases
Integrating Triggers and Declarative Constraints in SQL Database Sytems
VLDB '96 Proceedings of the 22th International Conference on Very Large Data Bases
Some Notes on Knowledge Assimilation in Deductive Databases
ILPS '97 International Seminar on Logic Databases and the Meaning of Change, Transactions and Change in Logic Databases
| Hi-index | 0.00 |
The lion's share of datalog features have been incorporated into the SQL3 standard proposal. However, most SQL manuals still recommend to implement user-defined conditions for data integrity nondeclaratively, by triggers or stored procedures. We describe how to implement known declarative database technology for integrity checking in SQL databases. We show how to represent and evaluate arbitrarily complex constraints in SQL without incurring major disadvantages usually associated to integrity checking in large databases. Error-prone procedural specification and laborious maintenance of integrity constraints is avoided by the declarativity of the specification language. The costs of evaluation is considerably reduced by an automated translation of declarative specifications to SQL triggers.