Electrical Engineering
      and Computer Sciences

Electrical Engineering and Computer Sciences

COLLEGE OF ENGINEERING

UC Berkeley

Version Modeling Using Production Rules in the POSTGRES DBMS

L-P. Ong

EECS Department
University of California, Berkeley
Technical Report No. UCB/ERL M91/51
1991

As noted in [STON80], versions (also called hypothetical relations) can be used to support "what if" scenarios in the database, and offer a mechanism for manipulating live data without fear of corrupting the database. In general, versions are implemented through differential files (deltas) [SEVR76], either via forward deltas [STON81, WOOD83], or via backward deltas [KATZ82]. The main drawback of version systems is that the semantics are desired. Furthermore, no single system is general enough to subsume all of the proposals. This thesis shows that production rules in a database system can be used to implement versions, and that such rules are general and flexible enough to accommodate any new semantics that the user might want.


BibTeX citation:

@techreport{Ong:M91/51,
    Author = {Ong, L-P.},
    Title = {Version Modeling Using Production Rules in the POSTGRES DBMS},
    Institution = {EECS Department, University of California, Berkeley},
    Year = {1991},
    URL = {http://www.eecs.berkeley.edu/Pubs/TechRpts/1991/1769.html},
    Number = {UCB/ERL M91/51},
    Abstract = {As noted in [STON80], versions (also called hypothetical relations) can be used to support "what if" scenarios in the database, and offer a mechanism for manipulating live data without fear of corrupting the database. In general, versions are implemented through differential files (deltas) [SEVR76], either via forward deltas [STON81, WOOD83], or via backward deltas [KATZ82]. The main drawback of version systems is that the semantics are desired. Furthermore, no single system is general enough to subsume all of the proposals. This thesis shows that production rules in a database system can be used to implement versions, and that such rules are general and flexible enough to accommodate any new semantics that the user might want.}
}

EndNote citation:

%0 Report
%A Ong, L-P.
%T Version Modeling Using Production Rules in the POSTGRES DBMS
%I EECS Department, University of California, Berkeley
%D 1991
%@ UCB/ERL M91/51
%U http://www.eecs.berkeley.edu/Pubs/TechRpts/1991/1769.html
%F Ong:M91/51