I'm pretty sure that the consensus is to never actually store the files in the database. What actual inconsistencies are you seeing that you are trying to fix?
On Mon, Sep 29, 2008 at 1:00 PM, Mark Stosberg <[EMAIL PROTECTED]> wrote: > > This question isn't so much a mod_perl question, as it is a question > about building high performance websites with Perl. > > We have a large, busy, database application that relates to millions of > photos, which we also need to store and display. We've been keeping the > meta data about the photos in PostgreSQL, and the files on the file > system. (Implemented much like CGI::Uploader ). > > This has worked great in terms of performance, but with so much data to > manage, over time we have run into data inconsistency issues between the > file system and the database. > > So, I'm asking if anyone has had experience successfully storing photos > (or othe files) directly in database? That would solve the consistency > issue, but may create a performance issue. Perhaps the right kind of > caching layer could solve that. > > Mark > > -- > . . . . . . . . . . . . . . . . . . . . . . . . . . . > Mark Stosberg Principal Developer > [EMAIL PROTECTED] Summersault, LLC > 765-939-9301 ext 202 database driven websites > . . . . . http://www.summersault.com/ . . . . . . . . > > > -- ~Tyler
