10 replies to this topic

[ahmedzoom99]

hi :

how i can retrieve image in my database using phpmyadmin


and there are any method better than phpmyadmin to make my database


thank you for helping me

[WingedPanther73]

You're going to have an issue with retreiving it, because the image is stored as binary data. PHPmyAdmin really wasn't meant for extracting that binary data, which could be an image, or a PDF, or a Word document. I would write a small PHP app to do that, instead.

As to how to make your database, that depends on the database. MySQL works well with PHPMyAdmin, but if you're using SQL Server or Oracle, then their tools would probably be best. I use SQuirreL SQL Client when working with databases, as it works with any of them quite well.

[VNFox]

I think you need to custom your app a littble ... pull it as binary data and convert it to image. I don't think there is any option in PhpMyAdmin to do this.

[lespauled]

I have to ask why you're storing images in a database? Normally, the database will contain a reference to an image, like it's location on the server or web. The overhead of storing and retrieving images from a DB is rather large.

[Orjan]

I have to ask why you're storing images in a database? Normally, the database will contain a reference to an image, like it's location on the server or web. The overhead of storing and retrieving images from a DB is rather large.

Storing images in DB can be very good at times. The images is easier to handle in one way, as you don't have to think about unique file names and much more. Also, a hacker which reach the file system don't find the images directly but need to search through the db for it. Also, the images isn't accessible by a url directly so you can build in a security layer in your server side language to prevent misusage etc.

[lespauled]

If security is a concern, put them in a location that is not accessible by the web server and write a script that handles security and serves up the files. When necessary, I write a httphandler to do just that.

There are many reason against storing images in a DB :

1. If your DB becomes corrupt to the point backups wont fix it, you loose your graphics as well as your data.
2. if there is any chance that you will migrate to a different database platform, your current BLOB format might be incompatible with, or at least a pain to convert to, the new format -- since, like web browsers, each vendor has implemented things with their own slant.

[Orjan]

Everything has pros and cons. You have to choose when to use the features and when not to. There is no such thing as the perfect condition for a feature,, and there is no feature that don't have a good occurance when to use it, otherwise it hadn't been created.

[lespauled]

My point is that it is frowned upon in the programming world. Of course anyone is free to architect their project as they wish. There are good practices and bad ones. Putting website graphics in a DB is a bad one.

[Orjan]

Well, the website graphics shouldn't be in a db, there I agree. But user pictures on a website can absolutely be stored in a db...

[Colanth]

In theory, theory and practice are the same. In practice they're different.

Storing images in DB can be very good at times.

In over 20 years, I've never found one.

The images is easier to handle in one way, as you don't have to think about unique file names and much more.

You never do - that's one thing computers are good at. You just let the computer create a unique name. (PHP even has a GUID function.)

Also, a hacker which reach the file system don't find the images directly but need to search through the db for it.

If the files aren't in your document path, he can't find the files.

Also, the images isn't accessible by a url directly so you can build in a security layer in your server side language to prevent misusage etc.

See above.

The main disadvantage is the terrific overwork you're putting on the database. Get hit by a few thousand requests for 10 images and your database is dying. (Never think that your website isn't going to be visited by thousands of people - doing so gives you a website you can't upgrade easily. Think AOL's or CNN's home page.)

"Designing for crash" usually results in crashes.

[Barnsite]

I have developed a database where images were required to be stored in the DB not in the file system, but only once. These were photos taken by surveyors.

This was due to the client specifying that the DB needed to be independent of it's environment, i.e. they did not have the control over the file system / folder structures and couldn't ensure that these would not change.

They also wanted all the data to be contained within the database back-up...