Using a version control system for your source code (like subversion) makes sense because it allows you to back out of mistakes, audit changes, make painless snapshots, discover exactly where something went wrong so that you can improve your process etc. For the same reasons it makes sense to do change tracking of business data, and many systems do so.
There are already a few questions on how to implement this on top of a normal database:
- Database structure to track change
history - Maintain history in a database
- Database history for client
usage - How to version control a record in a
database - …
For a feature that is so useful and popular, it seems strange that we all need to reinvent the wheel. Are there any existing database implementations which already solved this problem? I’m imagining that such a system would extend the SQL syntax to allow easy querying of the history.
Take a look at temporal databases, such as TimeDB.