Composite Event Specification in Active Databases: Model & Implementation

Active database systems require facilities to specify triggers that fire when specified events occur. We propose a language for specifying composite events as eveti expressions, formed using event operators and events (primitive or composite). An event expression maps an event history to anothe-r event history that contains only the events at which the event expression is “satisfied” and at which the trigger should 6re. We present several examples illustrating how quite complex event specifications are possible using event expressions. In addition to the basic event operators, we also provide facilities that make it easier to specify composite events. “Pipes” allow users to isolate sub-histories of interest. “Correlation variables” allow users to ensure that different parts of an event expression are satisfied by the same event, thereby facilitating the coordination of sub-events within a composite event. We show how to efficiently implement event expressions using finite automata. Each event causes an automaton to change state. When an automaton reaches an accepting state, a composite event of interest is recognized, and the corresponding trigger fired. Events have attributes. For primitive events, these could be parameters of the activity that caused the event, selected parts of the database state, or functions computed therefrom. For composite events, attributes are derived from the attributes of the constituent primitive events. These attributes can be used in checking conditions, and in any actions triggered. Event expressions can specify values (or sets or ranges of values) for particular attributes, and can even require that some attributes be equal. The composite event specified by the expression does not occur unless the specified condition on attributes is satisfied. Permission to copy withoutfee all or port of rhis material is granted provided that the copies are rwt made or distributed for direct commercial advantage. the VLDB copyright notice and the title of the pubkatum and its date appem. and notice L given that copying is by permission Of the Very Large Data BUM E&mm. TO copy othenvire. or w republish. reqtirer = fee on&r special permission from the Endowmmt. Proceedings of the 18th VLDB Conference Vancouver, British Columbia, Canada, 1992

[1]  C. J. Date A Guide to the SQL Standard , 1987 .

[2]  Balachander Krishnamurthy,et al.  An event-action model of computer-supported cooperative work: design and implementation , 1991 .

[3]  Hamid Pirahesh,et al.  Extensions to Starburst: objects, types, functions, and rules , 1991, CACM.

[4]  Catriel Beeri,et al.  Sets and negation in a logic data base language (LDL1) , 1987, PODS.

[5]  Umeshwar Dayal,et al.  The HiPAC project: combining active databases and timing constraints , 1988, SGMD.

[6]  Balachander Krishnamurthy,et al.  An event-based model of software configuration management , 1991, SCM '91.

[7]  Narain H. Gehani,et al.  Ode as an Active Database: Constraints and Triggers , 1991, VLDB.

[8]  Michael Stonebraker,et al.  The POSTGRES next generation database management system , 1991, CACM.

[9]  Umeshwar Dayal,et al.  A Transactional Model for Long-Running Activities , 1991, VLDB.

[10]  Catriel Beeri,et al.  A Model for Active Object Oriented Databases , 1991, VLDB.

[11]  Michael Stonebraker,et al.  Database systems: achievements and opportunities , 1990, SGMD.

[12]  Dov M. Gabbay,et al.  Temporal Logic & Historical Databases , 1991, VLDB.

[13]  Narain H. Gehani,et al.  Event specification in an active object-oriented database , 1992, SIGMOD '92.

[14]  Hamid Pirahesh,et al.  Alert: An Architecture for Transforming a Passive DBMS into an Active DBMS , 1991, VLDB.

[15]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[16]  Alasdair Urquhart,et al.  Temporal Logic , 1971 .