I can think of several instances where versioning a database as described might be useful if done carefully. For example, if you had a series of read only databases with read-only content (e.g. a catalog of specifications for parts), it might make sense then to version both the application that fronts the database and the database itself - particularly if there are major changes in the application between versions and your users were prone to being attached to older versions of the application...

Joe