Forum OpenACS Q&A: Status of file storage module?
about setting up a small site that would use it, and I'd like to have
an idea of what shape it's in before I start, since some people have
found that some of the more obscure modules aren't fully ported yet.
Plus, there's my philosophy that storing these files in the database is a mediocre idea at best. There is no need for transactional control over the file content. Thus, we have built new-file-storage, which stores all files in the filesystem, has a more logical permission scheme (permissions linked to files instead of versions of files), and is generally much faster. I'm happy to distribute this code, I just didn't want to add yet another new module to the distribution.
I see no reason to store the files in the DB, either. In fact, for my own website I store portraits in the filesystem rather than the DB for similar reasons, and I'm the guy who wrote the LOB hack!
I believe that aD is indeed working on a new version of file storage (if the slightly old documentation is to be believed, anyway), but it will have *more* emphasis on version control, not less. This suits my needs but clearly doesn't suit everyone's.
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...
BTW, out of curiosity, how does CVS store source code? In a database or a file system?