Almost everyone who writes code is familiar with source con trol systems which track the changes to source code over time. Within rel ational databases\, however\, about the best way to track changes to data is some form of history table. It turns out that all changes to specifie d data can be tracked\, maintained and viewed with minimal changes to the underlying model and few if any changes to existing apps (except\, of co urse\, those apps that are designed to work with "past" data or the histo ry tables themselves).
\nMake verisoning automatic\, transparent an d flawless\, with no compromising of data integrity -- including referenc ial integrity\, the big bugaboo of most versioning attempts. Get rid of a ll history tables and the triggers\, stored procedures and app code used to maintain them. In fact\, current data and past data are viewed with th e same query.
\nFor those familiar with bi-temporal concepts\, vers ioning is basically just implementing transaction time. However\, from ve rsioning to full bi-temporal functionality is a small step. For those int erested in full bi-temporal capability (transaction time and effective ti me) I will have have handouts available showing how to get the rest of th e way.
DTEND;TZID=America/Phoenix:20131109T163000 DTSTAMP:20260710T132227Z DTSTART;TZID=America/Phoenix:20131109T153000 GEO:33.293070;-111.796620 LOCATION:Chandler - Gilbert Community College - IRN-120 ORGANIZER: SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Almost everyone who writes code is familiar with source control systems which track the changes to source code over time. Within relatio nal databases\, however\, about the best way to track changes to data is some form of history table. It turns out that all changes to specified da ta can be tracked\, maintained and viewed with minimal changes to the und erlying model and few if any changes to existing apps (except\, of course \, those apps that are designed to work with "past" data or the history t ables themselves).
\nMake verisoning automatic\, transparent and fl awless\, with no compromising of data integrity -- including referencial integrity\, the big bugaboo of most versioning attempts. Get rid of all h istory tables and the triggers\, stored procedures and app code used to m aintain them. In fact\, current data and past data are viewed with the sa me query.
\nFor those familiar with bi-temporal concepts\, versioni ng is basically just implementing transaction time. However\, from versio ning to full bi-temporal functionality is a small step. For those interes ted in full bi-temporal capability (transaction time and effective time) I will have have handouts available showing how to get the rest of the wa y.
UID:d4485f52-fa2e-4807-baf7-d636d1598d66 END:VEVENT END:VCALENDAR