> Personally I think databases these days (MySQL in my experience at > least) are more than reliable enough and fast enough to serve up > binary data in quite large quantities. If you run into performance > issues, implement a caching solution run from a crontab.
I had a very, very bad experience with mySQL when a very simple table (inserts at 99%) that got over 350.000 rows (100MB). So I wouldn't say "MySQL in my experience at least". As I migrated that barely-lost table to postgreSQL (almost identical designs) it still goes on and currently has over 1.000.000 rows (400MB) Just my .002 EuroCents. The rest on why to keep the images in Db is a very good answer. Actually, it is so good that I might even write an article on this issue. Sincerely, Maxim Maletsky Founder, Chief Developer www.PHPBeginner.com // where PHP Begins -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
