I read a few messages about people that were having problems backing them
up. If you only have a link to the image, it is no prob to back up.
I've never tried to mysqldump an BLOB. Don't think I'd want to read that
printout!
Also, it seems to be a waste of database space.
Robert Dayton
Unconventional Solutions, Inc.
Creators of DForce
Internet Process Serving Software
88-30 Sutphin blvd
Jamaica, NY 11435
(718) 558-6081
(352) 343-0462
----- Original Message -----
From: "Irmund Thum" <[EMAIL PROTECTED]>
To: "Robert Dayton" <[EMAIL PROTECTED]>; "Chris Chabot"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, August 25, 2001 3:21 PM
Subject: Re: MySQL Still a wise choice for developers?
>
> > I would also strongly suggest not storing your images in the database
but
> > rather a link to the image.
>
> even that - why?
> if you're using an ultrafast webserver like Tux in combination with
> Apache/php-perl
> the Tux webserver serves the images incredibly fast (see specweb tests)
> what advantage is the storing of a link to images in a SQL database?
>
> i.t
---------------------------------------------------------------------
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
