But does having version control necessarily mean you have to store the body of the file in the database? I don't see any particular reason why you couldn't keep your versions on disk, using a renaming convention, and then maintain the rest of the information in the database.
The biggest problem with storing files in the database, IMHO, is that it makes your dump files *huge* very quickly. Since versions don't change once they're uploaded, if they were kept in disk files they would be backed up once and then skipped by incremental backups. In the database, where most of us do backups of full data dumps, you end up backing up those unchanged versions over and over and over...
