On Fri, 12 Mar 2004, Jigal van Hemert wrote:
> I've been reading this thread, but I can't see the advantages of storing > files in a database. > I've always had the impression that a *file* system was the appropriate > place to store files. Scalability, searching, security.. just a few.. > Replication seems more silly, since one also copies the stored files to the > slave. This not only adds to the traffic between slave and master, but also > wastes diskspace. Disk is relatively cheap.. And if your using mysql file storage on a large site you'll probably need replication to feed those data hungry frontend webservers.. > Furthermore large files may cause you to hit the max_allowed_packet size > (PDF's of 5MB or larger are no exception in real life). Anyone implementing mysql file storage using largeblobs, I feed needs to re-address their storage implementation. > I've built a system which includes the possibility of downloading one's own > bills in PDF format. This system runs on load balanced webservers with one > mysql server. The files are stored on a different machine that cannot be > accessed directly from the web. Scripts validate access to the PDF and serve > it to the client. Works like a charm ;-) Sweet.. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
