Hi, just a quick note.
> A) There's no *point* in keeping the image in the database.
> A DBMS is all about searching, comparing, relations, etc. You
> get *none* of these by storing the image data in the DB.
Correct if you have a small amount of images, problem if you
have thousands of these puppies in one directory. Solution
there of course is to split it up across other directories
or just change your fs type/
> B) Unless you're careful, you totally defeat both the
> web servers and the clients ability to make use of caching
> mechanisms. While you may not see a big difference on the
> server, it can make one h... of a difference to the user
> stuck behind a 33.6K modem.
So very true.
brett
--
================================================================
UNIX Ad/DBA/Teaboy/Analyst/Gopher - Intratex Holdings - Pinetown
Tel. +27 31 717 4000/4146 Fax. +27 31 717 4001
================================================================
Rule 1. Before calling me... if its a Windows box... REBOOT IT!
Rule 2. If its a Windows box... Don't call me...
Rule 3. Windows isn't much good for anything aside from games.
Rule 4. Repeat.
----------------------------------------------------------------
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
