Note that there are some explanatory texts on larger screens.

plurals
  1. POiPhone: To store photo album image URL's and compare later:
    text
    copied!<p>As per my query from the below link, i've implemented retrieving photo album images from ALAsset Library. </p> <p><a href="https://stackoverflow.com/questions/5442653/upload-alasset-url-images-to-the-server">Upload ALAsset URL images to the server</a></p> <p>I get the images Asset URL's like below, "assets-library://asset/asset.JPG?id=1000000001&amp;ext=JPG" "assets-library://asset/asset.JPG?id=1000000002&amp;ext=JPG" "assets-library://asset/asset.JPG?id=1000000003&amp;ext=JPG"</p> <p>I want to store these in a database (or) file [I don't know which is suitable for comparison for later purposes]. Next time(say,after 30 mins), i want to get again all the image URL's from Asset and compare with the previous image URL's which has stored in a DB, to find if any new images has been added in photo album or not. If any new image is been added in photo album, then i get that image in my code.</p> <p>I want to know, what should i use to store the image URL strings, whether SQLite database (or) file, and next time which one should be sufficient to compare the previous data and the current data? I thought of going with creating sqlite database and store the data and compare the image URL strings with the stored data like that …. Am i thinking right to go? If yes, may i know how to store the data(image URL strings) in a sqlite database and do comparison between new image URL's and stored data? I created a sqlite database through Firefox sqlite manager plugin and added a table. I'm not getting any samples further to go through to solve my purposes, i.e. store the image URL strings in sqlite database and do comparison between the stored image URL strings and new image URL strings which i got from Asset library.</p> <p>Please help and advise.</p> <p>Thank you!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload