K.P. Eswaran and D.D. Chamberlin. Functional specifications of a subsystem for data base integrity. In Proceedings of the First International Conference on Very Large Data Bases, pages 48--67, Framingham, Massachusetts, September 1975.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....SUPPORTER EMPLOYEE.PK 1 DEPEN DENT DEPENDENT.PK n EXISTENCE OF DEPENDENT DEPENDS ON EXISTENCE OF SUPPORTER WEAK ENTITY RELATION DEPENDENT NAME FIRST NAME EMPLOYEE.PK THROUGH EMPLOYEE DEPENDENT 3. 3 Implications on Data Integrity Some work has been done on data integrity for other models [8, 14, 16, 28]. With explicit concepts of entity and relationship, the entity relationship model will be useful in understanding and specifying constraints for maintaining data integrity. For example, there are three major kinds of constraints on values: 1) Constraints on allowable values for a value set. This ....

ESWARAN, K.P., AN) CHAMBERLIN, D.D. Functional specifications of a subsystem for data base integrity. Proc. Very Large Data Base Conf., Framingham, Mass., Sept. 1975, pp. 48-68.

....until the result appropriately reflects the integrity constraints and rules of the application domain. 6 Related Work The importance of the specification and enforcement of semantic integrity constraints in databases was already recognized and addressed in the mid seventies by several authors [36, 65, 24, 12, 17]. After these initial papers, semantic integrity constraints in databases have been studied from various aspects. The results of the different research efforts are documented in hundreds of papers. Several dissertations, e.g. 12, 22, 29, 37, 58, 45, 44, 69] and chapters in textbooks, e.g. 70, ....

K. P. Eswaran and D. D. Chamberlin. Functional Specifications of a Subsystem for Data Base Integrity. In D. S. Kerr, editor, Proc. of the 1st Int. Conf. on Very Large Data Bases, VLDB'75, September 24--24, 1975, Framingham, MA, USA, pages 48--68. Morgan Kaufmann Publishers, Los Altos, CA, 1975.

....constraints refer to all constraints on the data that must hold on each state of the database[7] Transition constraints specify the way in which one state of the database 9 can be transformed to another state. A rule ensuring monotonically increasing salary values is a transition constraint[33, 35 37]. We distinguish between integrity constraints and query transformation rules to provide a more accurate description of their nature. Query transformation rules are explicit state integrity constraints, which are useful for semantic query optimization for universally quantified queries. These ....

K. Eswaran and D. D. Chamberlin, Functional Specifications of a Subsystem for Database Integrity, VLDB, (1975).

....State constraints refer to all constraints on the data that must hold on each state of the database[7] Transition constraints constrain the way in which one state of the database can be transformed to another state. A rule ensuring monotonically increasing salary values is a transition constraint[32, 34 36]. We distinguish between integrity constraints and query transformation rules to provide a more accurate description of their nature. Query transformation rules are explicit state integrity constraints, which are useful for semantic query optimization for universally quantified queries. These ....

K. Eswaran and D. D. Chamberlin, Functional Specifications of a Subsystem for Database Integrity, VLDB, (1975).

.... until now one could only reject updates that led to inconsistent database states, our work is a natural development in the area of failure actions for semantic integrity constraints in data bases; it thus complements previous research on the specification and enforcement of such constraints [14] [10], 27] 9] 6] 2] 17] Allowing exceptions to persist raises a host of issues, which will be discussed in further detail in the next section, and which are a chief concern of this paper. Without going into details, we note here that we will rely on the general exception handling mechanism to ....

Eswaran, K.P. and Chamberlin, D.D. Functional specifications of a subsystem for data base integrity. In Proc. of Int. Conf. On VLDB, pages 48:67. Framingham, Mass., September, 1975.

....of the publication and its date appear, and notice is given that copying is by permission of the Very Large Data Base Endowment. To copy otherwise, or to republish, requires a fee and or special permission from the Endowment. Proceedings of the 22nd VLDB Conference Mumbai(Bombay) India, 1996 [3, 11, 34] promotes event condition action (ECA) rules as the uniform mechanism to support constraints, authorization and application logic. The only prior work that considers the simultaneous existence of separate specifications and models for the execution of ECA rules and declarative constraints is ....

K.P. Eswaran and D.D. Chamberlin. Functional specifications of a subsystem for data base integrity. In Proc. of the 1st Int. Conf. on Very Large Data Bases, pages 48--67, Framingham, Massachusetts, September 1975.

....process. Keywords Constraint Enforcement, Inconsistent Information, Model Based Diagnosis, Repairing Inconsistencies, Repair Strategies 1 INTRODUCTION Numerous papers have been written on specifying and maintaining integrity constraints in databases since the first large database conference (Eswaran and Chamberlin 1975, Hammer and McLeod 1975) for an overview see, e.g. Grefen and Apers 1993, Widom 1994) The aim has always been to develop c flIFIP 1996. Published by Chapman Hall 2 An Extensible Framework for Repairing Constraint Violations methods that efficiently check integrity constraints for ....

K. Eswaran, D. Chamberlin (1975) Functional Specifications of a Subsystem for Data Base Integrity. In D. Kerr (ed.), Proc. of the 1st International Conference on Very Large Data Bases, 48--68, Morgan Kaufmann Publishers, Los Altos, CA.

....active DBMSs. The first steps taken in this field were the ON conditions proposed by the CODASYL Data Description Language Committee in 1973 [COD73] In the following period some relational DBMSs were extended by an active part. One can distinguish triggers and assertions as proposed for System R [EC75, Esw76] to enforce integrity constraints and declarative rules to express relationships between data items. Active rule systems for object oriented DBMSs have also been developed. Two representatives of this class are SAMOS [GD93] and HiPAC [DBM88] SAMOS supports its own object oriented data ....

K.P. Eswaran and D.D. Chamgerlain. Functional Specifications of a Subsystem for Data Base Integrity. In Proc. Int. Conf. on Very Large Data Bases, September 1975.

..... 174 A.2 Strengthened Specification of an Elevator Controller . 175 vii Chapter 1 Introduction 1. 1 Motivation The maintenance of semantic integrity has been recognized as a cornerstone issue for the development of data bases and knowledge bases alike [Flo74] EC75] Ull88] MCPT91] Mat91] LNW91] Aimed at modeling a multitude of application domains, knowledge base management systems (hereafter KBMSs) will be required to represent consistently and reason efficiently with a large amount and a wide range of knowledge. Integrity constraints express ....

....the enforcement of transition or dynamic integrity constraints. Furthermore, the need for modeling evolving domains has given rise to challenging research issues relating to the incorporation of time in knowledge bases. The, by now wellestablished, notions of static and transitional integrity [EC75] Nic82] ELG84] must be generalized to that of temporal integrity. The problem of ensuring that the correctness criteria expressed by integrity constraints will not be violated in a dynamic environment now has an additional dimension, namely that of monitoring time dependent properties. Such ....

K. Eswaran and D. Chamberlin. Functional Specifications of a Subsystem for Database Integrity. In Proceedings of VLDB-75, pages 48--68, 1975.

.... rules in database systems allow specification of data manipulation operations that are automatically executed whenever certain events occur and or certain conditions are met [DE89, Han89,KdMS90,SJGP90,WF90] The usefulness of incorporating production rules into database systems is well accepted [EC75,MD89,Mor83], particularly in the context of constraint enforcement. However, we know of no automatic (or semi automatic) method for specifying general constraints in a high level, non procedural language, then deriving lower level production rules that maintain the constraints. We describe such a method. The ....

K.P. Eswaran and D.D. Chamberlin. Functional specifications of a subsystem for data base integrity. In Proc. of First VLDB, pages 48--67, September 1975.

....dangling reference exceptions, are supported by the mechanism, and also shows that the transactionboundary rule firing is supported. 6. 1 Active database technology Active database technology was originally proposed to strengthen the power of integrity enforcement by database management systems (Eswaran and Chamberlain 1975). Since then the concept was generalized to handle more general rules in HiPAC (McCarthy and Dayal 1989) POSTGRES (Stonebraker et al. 1990) Starburst (Widom 1996) and ODE (Agrawal and Gehani 1989) Among these, the HiPAC project proposed Event Condition Action (ECA) rules, as a general ....

Eswaran, K. P. and D. D. Chamberlain (1975, September). Functional specifications of a subsystem for data base integrity. In Proceedings of the First International Conference on Very Large Data Bases, pp. 48--68.

....the following two categories: 1. Specification of an event action pair : an action, typically the execution of a check and or correction procedure, is triggered whenever a certain event occurs. This action performs usually the insertion or deletion of specific information to or from the database [EC75]. 2. Specification of a first order formula : at any time, the specified first order formula must be true with respect to the contents of the database [Nic82] Clearly, the first approach is more general than the second, especially if we allow the action to be formulated in a general purpose ....

K. P. Eswaran and D. D. Chamberlin. Functional Specification of a Subsystem for Data Base Integrity. In Proc. Int. Conf. on Very Large Data Bases, pages 48--68, 1975.

....sequences of basic updates. Additional optimization steps exploit the organization of simplified forms in dependence graphs. 1 Introduction The maintenance of semantic integrity has been recognized as a cornerstone issue for the development of data bases and knowledge bases alike [Flo74] EC75] Ull88] MCP 94] Integrity constraints express application dependent semantics that are not built into the semantics of the knowledge representation language or the data structures used. Additionally, they constitute a means for controlling the quality of information stored in knowledge ....

K. Eswaran and D. Chamberlin. Functional Specifications of a Subsystem for Database Integrity. In Proceedings of the 1st International Conference in Very Large Databases, pages 48--68, 1975.

....languages (4GL) often combining descriptive and operational elements [45] Also graph grammars have been proposed for database action modelling [46] Only few approaches allow for a separate specification of dynamic integrity constraints to describe admissible evolutions of databases. In [47, 48, 49] transitional assertions are discussed, i.e. constraints restricting database state transitions. In [5] such constraints are integrated into Petri net based action specifications by special constructs. There also have been proposed modal logic styles as [38, 36, 50] and temporal logic based ....

....AIRPLANE s DateOfMaintenance contains the dates of its past maintenances. 11) A NON STOP FLIGHT must not be deleted from the database. There have been proposed a variety of styles for the specification of admissible database behaviour. Important directions in this area are transitional assertions [47, 48, 49] and Petri net approaches [43, 104, 5, 105] Another important direction is to specify long term behaviour in a descriptive, logic oriented way. The work in this direction was much inspired by the approaches in [106, 107, 108] proposing modal and temporal logic for program construction and ....

Eswaran, K.D. ; Chamberlin, D.D. Functional Specification of a Subsystem for Data Base Integrity. VLDB 1975 (48--68), 1975.

....the objects, ffl A: The events (activations) that cause checking of the constraint and ffl R: The reaction that is performed due to violation of the constraint. In addition to the number of considered database states, constraints can be classified by an number of other features as proposed in [EC75] HM76] and [SSMJ90] ffl Regarding their status w.r.t. the data model A modellinherent IC is expressed within the data model itself. A modellexternal IC is defined outside the data model 1 . ffl Regarding their time of satisfaction If the IC has to be satisfied after each atomic operation ....

K. P. Eswaran and D. Chamberlin. Functional specification of a subsystem for database integrity. In Proc. Intl. Conf. on Very Large Data Bases, pages 48--68, Framingham, Massachusetts, 1975.

No context found.

K.P. Eswaran and D.D. Chamberlin. Functional specifications of a subsystem for data base integrity. In Proceedings of the First International Conference on Very Large Data Bases, pages 48--67, Framingham, Massachusetts, September 1975.

No context found.

K.P. Eswaran and D.D. Chamberlain. Functional Specifications of a Subsystem for Data Base Integrity. Proc. 1975 VLDB Conf., Frammigham, Mass., September 1975.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC