I have, but then again I was using a @!#$!$ MS DBS at the time ;)
On Wed, 16 Mar 2005, Andrew Huntwork wrote: > it looks like the clear consensus is file system. that's what 2 of my > co-workers said before i asked here, but now i actually basically > believe them. > > I still have my doubts though...if someone has done this the db way and > actually seen real scalability problems, i'd love to hear about it. > > Thanks for the responses. > > Andrew Huntwork wrote: > > I'm writing this web app that allows users to upload documents, such as > > word docs, images, etc, and then to download those documents again on > > request. the documents are not searched, interpretted, processed, > > version controlled, or anything else. just upload and download. i > > wonder if there's a general rule on whether one should stick such things > > into a db or onto the file system. > > > > i currently favor sticking them in the db. putting them on the fs seems > > to interfere with clustering (different files would be on different > > filesystems). it's also another thing to back up and generally > > maintain. on the other hand putting them in the db puts extra load on > > the db and the network. there are a bunch of other issues too. > > > > Any ideas? Thanks for any help. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
