i want to display around 1000+ images into an application. Which is the most effective way to store images, on device or in database ?
I am using sqlite database in my app.
Store your image on server than download it in device, save your image into sdcard as a cache or simple image. At download on single success of image store its path into your table and used in your application.
Use Lazy loading concept to load image in application. Its better to store image in sdcard rather than in database.
In android or ios dont save large images into database In sqlite or in core data it can lead to database inconsistency and the database like sqlite are not designed for saving large images.
In android use
Internal Storage or External Storage
In ios use
iOS File System
It will be better if you store the image in server. But if you dont have access to a server, then store the image path in SQLite database and have the images in sdcard. It is always a good programming practice to do like this.
Related
I'm using sqlite db in my app and now I would like to allow user customize the background image make them able to select one from their gallery.
Should I just store the path to image and simpy refer to it every time or should I some how transfer the image to some text and store it completely in my db? The second option prevents in case of picture being deleted from gallery. But I would like to know the most appropriate way of doing that.
SQLite has a cursor limit of 1Mb. So, you will probably not be able to store it completely in the DB, when you go to to request it will probably be truncated. Store the path to the image in the database table, and access it that way.
You wouldn't store it as text. Store it as blob to your database. In my opinion this is the way to go (if you use SQLite anyway).
If you have large images then store the path to your storage and not the image to the database.
I think it would be better to save only the path of the background, you won't be limited by the size of the image
In my opinion, the best way to save the customized background image is copy it into the internal storage (private storage) of your application. If you store only the path of the file, then file cannot be available once the user deleted that.
The official docs saying about the internal storage is:
It's always available.
Files saved here are accessible by only your app by default.
When the user uninstalls your app, the system removes all your app's files from internal storage.
I need some suggestion here on the Sql database approach for storing rss feed data
First : My rss feeds gives image url links which i diplay using bitmap and inputstream at runtime but now for offline purposes so as to use app when internet not available how do i load them, do i need to save complete images like whatsapp does right ? is this approach right ? if yes how to save complete images in database ? a sample code will help.
Last i want to save the complete database on sd card not in internal memory , storing data on sd card will work fine or it will create problem ? because whatsapp or many other apps stores quite a data in internal memory !! if storing on sd card is not a problem how do i store complete data on sd card ?
If your image comes from your online server, use cache then save the URL to your SQLite database together with the other data you need to access when offline.
As for the downloading and caching approach for images you can see this link:
http://theandroidcoder.com/utilities/android-image-download-and-caching
Once the image is downloaded and cached you can view it even offline. :) Or else you may want to store the whole image and save it in a specific path on your phone and access it when internet connection is not present.
As for your idea on storing in SD card. there is only one problem I can think about. When the SD card is removed, all your data is lost. You should search on how to better handle data on your phone as well as do as research on storing in external storage for this one. It's now on your end to do some research about it to further understand its risk and advantages.
I have a question about saving images in an SQLite database location in the app.
I made an app for iOS where users can snap a photo or grab an existing one from the app that saves them in a local bank in own app, since the IOS does not have so many problems with disk space.
On Android already have code that takes the photo or use an existing one, now wanted to know how save them in SQLite database. (?)
I've been reading about and some suggest saving the image in SD card and insert into the database only the image path, but if for some reason it is excluded from the SD card will have an error in your application for the path referenced no longer exists.
What would be the ideal solution for this?
You should only keep the name of the picture in the database and store the picture on the internal storage, not on the sdcard, save them in the first place as private to your application only.
The ideal solution is to store it in the SD card. Storing in DB won't keep the user from deleting it. You'll also lose this information if the user clears the app data. All databases are deleted when the user does it.
Anyway, if you choose the SQLite solution, you can use a blob field. Remember that some versions of SQLite won't support large blob data. Check this out:
http://effbot.org/zone/sqlite-blob.htm
I also suggest this:
http://developer.android.com/training/displaying-bitmaps/cache-bitmap.html
May I know how to store an image manually into a database without using codes/programming? How do I go about doing that? How do I even save it as a BLOB type? Or do I save the image URL(from local desktop location and not from the internet) to the database? And after which, how do I go about displaying the image from the preloaded database and display it in the image view?
Many thanks in advance!
I suppose you want to store images on your device, am i wright? As for me the best practice is to save them on SD card and remember the path in DB.
For easy saving you can use bitmap map method compress which receives outputstream to sd card path as a parameter
I have managed to find alternatives to settle down with. Which is to save the image file name into the database and store the images in the application's asset folder after which display the image by the path name in webview.
Hi i want to store an image in my android application.I am confused that should i store it in the database or in an application folder?which is a better option and y??
Store it on the SDCard if possible else use application folder.
It depends from the type of image you will want to store. It's confidentially? Or public?
Create a database only for saving an image it would be non-optimal, but it you have a database created, for example to save user profiles (name, surname, birthday, etc), it could be a great option to save a profile image in the database.
Anyway, i think sdcard is the best option. And create a custom folder for your application and save all the images there ;)
Hope this helps...
Its depends on the size of images, you want to provide security to that images etc..
If not bother then store images in a application folder /asset , /drawable or external storage (If use external storage then save path of those images in database) and use it directly, To store in database is quite some ugly way, convert it into blob type and then store, re fetching from database convert into byte to bitmap..