1995], the goal was to develop a proposal for the SQL/ Temporal part of SQL3 [Snodgrass et al.
Earlier decendants of the work described in this article are the change proposals submitted to the SQL/Temporal part of SQL3 [Snodgrass et al.
Final Committee Draft Editing Meeting," Database.
We should perhaps emphasize the fact that despite (or perhaps because of) the last point, our model is not what is sometimes referred to as "subtables and supertables." We regard the subtables and supertables idea (which is currently supported in SQL3) as a totally separate phenomenon, one that might be interesting (though we are skeptical) but which has nothing to do with type inheritance per se.
SQL3 Committee Drafts can be found at the SQL website: ftp://jerry.ece.umassd, edu/isowg3/ dbl/BASEdocs/public
Collections of objects in SQL3
. In Proceedings of the Nineteenth International Conference on Very Large Data Bases (VLDB '93, Dublin, Ireland, Aug.).
The specification of triggers in SQL:1999 (formerly known as SQL3) has migrated significantly over the years (e.g., see the SQL3 draft descriptions in Widom and Ceri  versus Kulkarni et al.
Earlier versions of the SQL3 draft specified compile-time syntactic restrictions on trigger definition to guarantee termination of trigger execution [Widom and Ceri 1996].
--Data manipulation events are captured by simple row-level granularity triggers as currently defined in the SQL3 standard; each Chimera-Exc data manipulation event is translated into a corresponding database trigger [Cochrane et al.
Active rules in these systems support basic functionality and are inspired by the forthcoming SQL3 standard [Cochrane et al.
Finally, we show that the approach is general, by applying it to the temporal query language constructs being proposed for SQL3.
In this section, we consider a variant of TSQL2 that is being proposed for incorporation into the SQL3 standard [Snodgrass et al.