title: Android: Saving images into Sqlite database
body: <p>im wondering if storing images as BLOB in the sqlite database would be a good idea?
  Does anybody has performance - experience with storing images (blob).</p>
  
  <p>My android app would be a small one, which will need to handle 20 to 100 images (100 kb up to 1MB per image). Worst case: I would say, that my database could reach a size of 100 MB. Does this has significant impact on the database performance?
  Average case: I guess the average user of my app has 40 images with 200 kb per image, so the size of database would be around 8 MB.
  Btw. of course the database stores also other "normal" data, so its not a image database only :)</p>
  
  <p>Is storing the path to the image which is stored on the storage(internal or sd card) a better approach? I guess that retrieving the image file path from the database and open and load the image from file would be a little bit slower (but not really significant, since I need to load only two images at once).</p>
  
  <p>A second question: 
  If I would use the second approach (store the path to image file in the database and load the image file):
  Does a disk cache (DiskLruCache) is something useful in this scenario? Would it bring a significant performance boost? My understanding is that a Disk cache would store bitmaps (instead of encoded jpg or png) and therefore a disc cache would load a bitmap directly from storeage and my app would save the time to decode the image(jpg or png). Is that correct? 
  Btw. In the "database approach" i would store the image already decoded as bitmap. So it seems to me to be something similar as the disc cache, isnt it?</p>
  
  <p>Edit:
  I forgot to tell you, that i need to store the images persistent on the device. Im not talking about caching images that for example I have retrieved from a web service ...</p>