This seems a good approach when you own all the code and the database. However, there are many times when you don't completely own one or both of these - eg. linking into a corporate database that the webdevs can't change or using a CMS that is mostly written by other people. In those situations it becomes really difficult to do decent versioning, and I've yet to see a good way of handling Drupal databases in version control.