Code

Changes between Version 4 and Version 5 of FullHistory


Ignore:
Timestamp:
07/17/06 19:19:33 (8 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FullHistory

    v4 v5  
    1919||Getting the API to work as described below|| 
    2020||Getting the code to a working state|| 
     21 
     22=== Discussion === 
     23The ability to keep previous states of a table accessible is well described in Richard T. Snodgrass's (http://www.cs.arizona.edu/~rts/) "Developing Time-Oriented Database Applications in SQL" (http://www.cs.arizona.edu/people/rts/tdbbook.pdf). Adding the ability to designate a particular model as a transaction-time state table, with suitable methods added to the model's API, and with all queries defaulting to using either the current time or the latest time. 
    2124 
    2225== Introduction == 
     
    8083 
    8184 
    82 === Discussion === 
    83  
    84 The ability to keep previous states of a table accessible is well described in Richard T. Snodgrass's (http://www.cs.arizona.edu/~rts/) "Developing Time-Oriented Database Applications in SQL" (http://www.cs.arizona.edu/people/rts/tdbbook.pdf). Adding the ability to designate a particular model as a transaction-time state table, with suitable methods added to the model's API, and with all queries defaulting to using either the current time or the latest time.