There are two different ways that you can handle images that are related to your database content - you can store the images in the database itself or you can store the images separately and just place the address of the image in the database.There are advantages and disadvantages to both of these approaches and so which you decide will depend on the relative importance of these pros and cons to your particular application.
Let's start by looking at the disadvantages of storing images in the database itself.
The disadvantages of storing the images separately include:
The advantages to each of the two alternatives are basically that each overcomes the disadvantages of the other. I could have just as easily reversed the above two lists and gave them as the advantages of doing things the opposite way. The reason I have listed everything as disadvantages of one or other of the methods though is that it is in order to overcome a particular disadvantage that one of the two approaches has that is what is most likely to lead to your selecting which of the two alternatives to use and so listing what each can't handle properly seemed the more useful way of presenting the information.
So which of the two ways of handling images that you choose to use will basically depend on which of the above two lists of disadvantages that you decide you can accept.
This article written by Stephen Chapman, Felgall Pty Ltd.