BLOB

Anon

How should I place into BLOB type of MYSQL one picture. Can you please show an example code?

Thank you

brandonschnell

http://www.phpbuilder.com/columns/florian19991014.php3

[deleted]

You shouldn't.

Putting images in a database is a bad idea.

darkness

Ive been thinking of putting images into a database i just havent got round to making the images, why is putting them into a database a bad idea and how else could i code it so that when i upload an image i wont have to change any code??

Anon

Thank you very much Brandon

Anon

Yeah, why this is not good?

[deleted]

Because by putting images into a database you are only generating overhead.

The only way to get images back out of the database to display them, is by running a script that executes a query that fetches the data from the database and sends it to the client. (This means no caching at all!)

That means that if you have 12 images on your page, you will need to run 12 extra scripts with 12 extra queries to display the full page.

If 15 people view a page at the same time, you get 12*15 = 180 queries at the same time, which is nearly double the default max of MySQL.

Bottom line: putting images in a database gives you NO advantage at all. The filesystem is faster and uses fewer resources.

Don't put your images in a database, but instead put only yhe name and location of the image in the database. Then when you display a page you can print IMG tags that link directly to the image on disk, so the webserver can serve the images. The filesystem will cache the files to make it even faster.

thewitt

This is an automatic response with Vincent, citing "poor performance" argument whenever anyone mentions putting images in a database.

It very much depends on your application, the size of your images, and how they are used.

There are cases, take icons for example, where the file system overhead for thousands or even millions of images is far more expensive than delivering the images from the database. Why should the file system have to support over 1,000,000 file handles for icons or small images, when you can store and deliver these much more efficently from a database.

On the other hand, you would be foolish to load 10M+ images into database tables without a real hard reason to do so.

If you have an application need to put images in a database, go right ahead. It works fine.

I have a number of applications where image storage is in mySQL, Oracle or Sybase databases, and in many cases, the delivery of the image from the database outperforms the same delivery from the filesystem by more than an order of magnitude.

Your application and your data will determine the best method to use for you.

-t

[deleted]

lol