Hi again, I guess one really good reason for not storing images directly in
a db table is performance. When you store a blob in a table it affects the
whole database's performance. It slows it down, that's why the most common
method is to store the images in a dir on the webserver and store only
EMAIL PROTECTED]]
Sent: Wednesday, January 16, 2002 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: [PHP] Re: Image Fields and PHP...
It basically comes down to speed. While there is nothing "Technicaly" wrong with
storing the images in the database, accessing the images will become slower as
Zara E" <[EMAIL PROTECTED]>
To: "'Lerp'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, January 16, 2002 1:52 PM
Subject: RE: [PHP] Re: Image Fields and PHP...
> Joe (And/Or others),
>
> We are storing the actual images in the DB. We did not w
PROTECTED]]
Sent: Wednesday, January 16, 2002 2:17 PM
To: [EMAIL PROTECTED]
Subject: [PHP] Re: Image Fields and PHP...
Hi Zara, are you storing a path to the images in your db? Or the actual image?
It's recommended that you stay away from storing actual images in the db. If you
are storing a
Hi Zara, are you storing a path to the images in your db? Or the actual
image? It's recommended that you stay away from storing actual images in the
db. If you are
storing a path the code below might help you out. It select a firstname, and
an image according to an id. You'll have to change the
5 matches
Mail list logo
