updating images!!!

Anon

Hi...which is better? To keep the images on database or on a different folder!!!
And if I keep them on a folder how can I have them on my dynamic web page?? Need some PHP scripts... Thanks.

gushy

Well I'm not gonna give you scripts just yet, I believe it's much better (and more fun & educational) to find out yourself. What I will do is give you pointers.

To be honest as far as speed is concerned there isn't much difference (I don't think, but I could be wrong), however I keep images in a seperate folder and just keep the path to the images in the database.

It really is a matter of preference. I do it this way because I can get the database query over and done with relatively quickly and build the page, it's then up to the webserver to pull the images.

Hope that helps you.

-- Nick Gushlow

[deleted]

Put the images where they belong: in the filesystem.
A database is meant to let you search data. When did you ever search through a binary?

Use the database only to find where the image is stored, and then access the image from disk directly.

This is very much faster than getting the image from the database, because the HTML code can point straight to the image on disk.
When you have the images in the database, there must always he a seperate script that fecthes the image from the database and prints it to the screen.

truehand

While initially it may not make much difference in speed to put the images in a database, eventually, you will start to see a big performance slowdown. The main issue is that as the database increases in size, the time to lookup the images (even in an indexed database) becomes increasingly higher. This is greatly emphasized in adding records. Basically, at a certain point it will take several times longer to add a record than to look one up.

Putting the images on the filesystem is ideal as that is what the filesystem was designed to do. Database are not well designed to perform queries on large blocks of binary data. Go figure.

jhonrputra

Hi....

Putting images on database is not good idea. The problem will gonna be worst if the size of the image is too fat!

If you put the images on database, they automatically become BLOB type. In PHP, if you want to show the images from the database [BLOB], you wont be satisfied. Because, the images will look bad! PHP has the limitation about size / resolution and size of BLOB. And, you cannot print/show the BLOB/Images with the rest table value. If you do so, you just see the another field's value and binary code of your BLOB! [scary hah...]

[deleted]

If you put the images on database, they automatically become BLOB type.
In PHP, if you want to show the images from the database [BLOB], you wont
be satisfied. Because, the images will look bad! PHP has the limitation about >size/ resolution and size of BLOB.

Total nonsense.

jhonrputra

Very short, sharp comment! Thanx...

By the way, why you don't give us how to show the content of BLOB and other fields value without separate script. As you told before, we can show BLOB with separate script. I used it before, and still now. But perhaps, if anyone who wants to save the images on BLOB, please consider about the system, size, and performance of your programs [in this case, perhaps we have the same idea].

Thanks anyway.