Language features for flexible handling of exceptions in information systems

An exception-handling facility suitable for languages used to implement database-intensive information systems is presented. Such a mechanism facilitates the development and maintenance of more flexible software systems by supporting the abstraction of details concerning special or abnormal occurrences. The type constraints imposed by the schema as well as various semantic integrity assertions are considered to be normalcy conditions, and the key contribution of this work is to allow exceptions to these constraints to persist. To achieve this, solutions are proposed to a range of problems, including sharing and computing with exceptional information, exception handling by users, the logic of constraints with exceptions, and implementation issues. The use of exception handling in dealing with null values, estimates, and measurement is also illustrated.

[1]  Daniel G. Bobrow,et al.  A model and stack implementation of multiple environments , 1973, CACM.

[2]  Andrzej Grzegorczyk.  An Outline of Mathematical Logic , 1974 .

[3]  A. Grzegorczyk.  An Outline of Mathematical Logic , 1974, Springer Netherlands.

[4]  John B. Goodenough,et al.  Exception handling: issues and a proposed notation , 1975, CACM.

[5]  Dennis McLeod,et al.  Semantic integrity in a relational data base system , 1975, VLDB '75.

[6]  Michael Stonebraker,et al.  Implementation of integrity constraints and views by query modification , 1975, SIGMOD '75.

[7]  Donald D. Chamberlin,et al.  Functional specifications of a subsystem for data base integrity , 1975, VLDB '75.

[8]  Roy Levin.  Program structures for exceptional condition handling , 1977 .

[9]  Diane C. P. Smith,et al.  Database abstractions: aggregation and generalization , 1977, TODS.

[10]  S. P. Schwartz.  Naming, necessity, and natural kinds , 1977 .

[11]  William Kent,et al.  Limitations of record-based information models , 1979, TODS.

[12]  Eric K. Clemons,et al.  Efficiently monitoring relational databases , 1979, ACM Trans. Database Syst..

[13]  Brian A. Wichmann,et al.  Rationale for the design of the Ada programming language , 1979, SIGP.

[14]  Alan Snyder,et al.  Exception Handling in CLU , 1979, IEEE Transactions on Software Engineering.

[15]  Edmund M. Clarke,et al.  Fast Maintenance of Semantic Integrity Assertions Using Redundant Aggregate Data , 1980, VLDB.

[16]  John Mylopoulos,et al.  A language facility for designing database-intensive applications , 1980, TODS.

[17]  Michael L. Brodie.  On Modelling Behavioural Semantics of Databases , 1981, VLDB.

[18]  Irving L. Traiger,et al.  The Recovery Manager of the System R Database Manager , 1981, CSUR.

[19]  Jay S. Kunin.  Analysis and specification of office procedures , 1982 .

[20]  Stephen Fox,et al.  Storage and Access Structures to Support a Semantic Data Model , 1982, VLDB.

[21]  Raymond Reiter,et al.  Towards a Logical Reconstruction of Relational Database Theory , 1982, On Conceptual Modelling.

[22]  Carlo Zaniolo.  Database relations with null values , 1982, PODS '82.

[23]  Flaviu Cristian,et al.  Exception Handling and Software Fault Tolerance , 1982, IEEE Transactions on Computers.

[24]  Carlo Zaniolo,et al.  Database relations with null values , 1982, J. Comput. Syst. Sci..

[25]  Alexander Borgida,et al.  The Darwin software-evolution environment , 1984 .

[26]  Daniel M. Berry,et al.  A modular verifiable exception handling mechanism , 1985, TOPL.

[27]  Renzo Orsini,et al.  GALILEO: a strongly-typed, interactive conceptual language , 1985, TODS.

[28]  Alexander Borgida,et al.  Features Of Languages for the Development of Information Systems at the conceptual Level , 1985, IEEE Software.