I think a good deal depends on the size of the image files themselves. There
are a number of apps that store small files (i.e.: icons, small gif's,
etc.), which seems to make sense.

Larger files may be problematic. There was quite a discussion on this issue
here just last week ... do a search of the list archive for 'blob versus
file' and read some informed opinions.

Gerald Jensen

----- Original Message -----
From: "René Fournier" <[EMAIL PROTECTED]>
Sent: Monday, July 08, 2002 5:34 PM
Subject: Storing images in MySQL bad idea, performance-wise?

I'm working on a simple content management system that uses PHP and
MySQL for updating a web site's text (stored in a MySQL database). (The
PHP scripts that do the updating (my stuf) live on one web server, the
actual DB data to be updated (my client's stuff) live on another.) So
far, I've only had to he able to update the text content of a
site--therefore, I've only had to bother to store textual data in the
client's DB. But now the client wants to be able to upload/change/delete
certain pictures on their web site--using my CMS tool--so I am faced
with the following problem:

Do I store all such images in the DB? (Which I understand reduces

Or do I--somehow--store the images as files on the client's web server?
And if so, how? (Because my PHP scripts are being executed on a
different server.)


René Fournier,

Toll-free +1.888.886.2754
Tel +1.403.291.3601
Fax +1.403.250.5228

SmartSlitters International
#33, 1339 - 40th Ave NE
Calgary AB  T2E 8N6

Before posting, please check:   (the manual)           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
Trouble unsubscribing? Try:

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to