> 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?
Basically you are allowing the database to wrap up your images. I, personally, have never seen the need to store images into the database. I tend to store locations to the images. Then you just have the webserver handle the request for the image instead of calling apache -> php -> database -> php -> apache...seems easier to just allow the client to grab the images. If you need to make modifications for the image, I usually do that 1x and then save the image off when for later use. For example, if you need to create thumbs or other images types. If you have tons of images..then you can setup the file system to deal with them (remembers the days of 24tb of images). -- thebigdog _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
