Right, certain things is beter to keep in the Db. Keep present that the file system is limited. You can't just have an unlimited amount of files on the same directory.
PostgreSQL is the best choice on my opinion. mySQL might fail on a large DB. Sincerely, Maxim Maletsky Founder, Chief Developer www.PHPBeginner.com // where PHP Begins -----Original Message----- From: Richard Archer [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 12:41 PM To: [EMAIL PROTECTED] Subject: Re: [PHP] Database and files At 11:25 AM +0100 22/4/02, Danny Shepherd wrote: >If you get multiple requests for files, expect the db to fall over very >quickly - what's wrong with storing them on the filesystem and having a >list of them in the db? If your DB falls over, get a better one. You wouldn't do this with Access, but MySQL or PostgreSQL will handle this with no problems. And storing them in the file system requires the web server process to have write access to the directory in which the files are stored. And so will any other users on that server. Security nightmare. >One thing - note that that the header names and the actual mimetype are >in lower case. Got weird results with anything different. Interesting tip. I'll try that out on Mac IE which never did download properly, IIRC. ...R. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
