if the images are not to big I would recommend saving them to blobs. It
saves you a lot of work, since you have to think about lots of stuff. Even a
garbage collector should be programmed since there is not a transaction
possibility between FS and DB.


"René fournier" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
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

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to