0

Possible Duplicate:
Storing Images in DB - Yea or Nay?

I am building a system in which the users can upload their own avatars. I found that there are 2 ways of doing that - storing the image into the database or storing actual path to the image in the database and saving the image on the hard drive. I am wondering which of these ways to use. So which of them is better and which of them should I choose?

Community
  • 1
  • 1
Nikolay
  • 89
  • 1
  • 3
  • Why don't you check this discussion, it is same as your question: http://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay – Tarik Sep 01 '11 at 19:01

3 Answers3

1

The normal way to do this is the 2nd one, it's too much strain on the DB to be storing the complete image as a BLOB, simply store the image on your webroot and the path in your DB table

8vius
  • 5,786
  • 14
  • 74
  • 136
0

I wouldn't store the images in a database, as 8vius points out, it's too much strain on the database. Instead of storing the path in the database, you could also retrieve the images by some logical algorithm. For example, if your users have a unique identifier you can contruct the path to the image with that. So if your user has id 1080, the path would be something like /avatars/1080.png

By the way, are you familiar with gravatar.com? If it suits your needs, it will save you the trouble of building the feature yourself.

Robin van der Knaap
  • 4,060
  • 2
  • 33
  • 48
0

Both ways works fine. It's more a matter of organization in my opinion. For example, you can backup you images within your data at once if it is on your database, but is really strain -like they said - but it's a advantage.