BEGIN:VCALENDAR
PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Phoenix
X-LIC-LOCATION:America/Phoenix
END:VTIMEZONE
BEGIN:VEVENT
DESCRIPTION:The ability to track changes in data over time has long been a
  goal in the relational database world. We have even written special temp
 oral databases with a special version of SQL to give us that ability. The
  rest of us have used history tables of one form or another to hold the p
 ast. But this separates current data from past data and can make analysis
  using both somewhat awkward.&#13\;&#10\;&#13\;&#10\;So it's handy to kno
 w that full bi-temporal capabilities can be brought to a standard RDBMS s
 ystem where we can access current and past data with the same query\, fro
 m the same sources.&#13\;&#10\;&#13\;&#10\;&quot\;Bi-temporal&quot\; mean
 s there are two ways to look back at past data. &quot\;Transaction time&q
 uot\; means we look at the data as it was stored in the database on a par
 ticular date and time. &quot\;Valid time&quot\; means we look back at the
  data that was in effect in the real world on a particular date and time\
 , even though there could have been some delay in updating the database.&
 #13\;&#10\;&#13\;&#10\;It would be helpful but not necessary to also atte
 nd the &quot\;Data Integrity: the Row Spanning Dependency antipattern&quo
 t\; session. We will briefly examine this common mistake used in most tim
 e-sensitive implementations\, but there is enough useful information that
  it has its own session for a more complete examination.
DTEND;TZID=America/Phoenix:20140405T174500
DTSTAMP:20260519T062059Z
DTSTART;TZID=America/Phoenix:20140405T164500
GEO:33.293070;-111.796620
LOCATION:Chandler - Gilbert Community College - IRN-128
ORGANIZER:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:The ability to track changes in data over time has long been a goa
 l in the relational database world. We have even written special temporal
  databases with a special version of SQL to give us that ability. The res
 t of us have used history tables of one form or another to hold the past.
  But this separates current data from past data and can make analysis usi
 ng both somewhat awkward.&#13\;&#10\;&#13\;&#10\;So it's handy to know th
 at full bi-temporal capabilities can be brought to a standard RDBMS syste
 m where we can access current and past data with the same query\, from th
 e same sources.&#13\;&#10\;&#13\;&#10\;&quot\;Bi-temporal&quot\; means th
 ere are two ways to look back at past data. &quot\;Transaction time&quot\
 ; means we look at the data as it was stored in the database on a particu
 lar date and time. &quot\;Valid time&quot\; means we look back at the dat
 a that was in effect in the real world on a particular date and time\, ev
 en though there could have been some delay in updating the database.&#13\
 ;&#10\;&#13\;&#10\;It would be helpful but not necessary to also attend t
 he &quot\;Data Integrity: the Row Spanning Dependency antipattern&quot\; 
 session. We will briefly examine this common mistake used in most time-se
 nsitive implementations\, but there is enough useful information that it 
 has its own session for a more complete examination.
UID:28b7d8b2-de74-4ead-a718-533e33ef4aae
END:VEVENT
END:VCALENDAR