Because It can be a shared resource, it can handle requests on the localhost or by vmware images in the same way. I don't have to create a bunch of symlinks to folders and use nfs/samba for vmware images It is password protected I can easily attach additional information to a file, without actually touching the file I can use foreign keys to handle garbage collection of files I can easily manage additional versions of files... For instance I could cache different versions of a image.
All in all I think it would just be much easier to manage a large set of files in a database, rather than a filesystem - Sean On Wed, Jul 29, 2009 at 3:00 PM, Wade Preston Shearer < [email protected]> wrote: > What are the reasons that you are even considering putting them in a DB? > > > > On 29 Jul 2009, at 14:42, Sean Thayne wrote: > > Hey All, >> I've recently been doing research of whether or not to store uploading >> files >> to a database or to just save them to a file and save the filename to the >> db. I have read that postgres becomes very unstable with 2mb+ files but >> that >> mysql can easily handle large files. >> >> I work with a project that allows 300+ employees to upload images and >> documents. They need to be highly secured and they are used by multiple >> sites including some vmware images, so I figure that by using a mysql >> database to store the files it will keep them protected and keep >> everything >> tightly tied together. >> >> But I still wonder if there are any cons to storing the files in a >> databases? >> >> >> >> Thanks, >> >> - Sean >> >> _______________________________________________ >> >> UPHPU mailing list >> [email protected] >> http://uphpu.org/mailman/listinfo/uphpu >> IRC: #uphpu on irc.freenode.net >> > > _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
