4 ms·
I'd like to add that there should also be a consideration for names that change over time. People get married and divorced, or courses might change their name b
by moron4hire 12y ago
I'd like to add that there should also be a consideration for names that change over time. People get married and divorced, or courses might change their name but not their number, or maybe there was just a data entry error but we need to keep record that the error was in place at that certain time (if you've ever had to deal with Sarbanes-Oxley compliant systems, you'll know what I mean).
There are physical entities in the world and what we call them is almost always completely arbitrary. So almost all databases that deal with real people and things over time need to be Temporal Databases[0].
It can be a pain in the butt to have to emulate a TRDBMS on a RDBMS, but if you get the design down right it will also save your butt way down the road.
[0] http://en.wikipedia.org/wiki/Temporal_database http://en.wikipedia.org/wiki/Temporal_database