This looks to me like a very strange approach, why not load from the web only the changed data in JSON, xml or any other formats and run a db update according to the changed data?
Edit: answer to your question in the comment:
I guess you should learn some sql first and some serveside language (my language of choice is python, but many would choose ruby, don't go php..) and then find the right software architecture. either using REST api exposing an online db, and use the data to sql UPDATE the local db once in a while or use it directly in the app (offloading more work to the server, but paying in latency). you could also use mongodb (a NOSQL db) in the server side and query directly with REST. or just load a JSON with all the data you need, once a week and use it as a kind of a local db instead of sqlite. no short answer or short way to answer your question. you should learn different technologies, and decide which is the correct way for your specific usecase. but any technology stack would probably include somekind of:
- server side db (and perhaps some logic)
- a way to expose the db and (REST? websockets? file downloads?) query new data from the server and update it with new data.
- security, authorization, authentication etc level to protect the server db and logic
app local db (sqllite, just an object containing data,local static files any other way), can be very minimal and resides in memory and can be the whole app.
the app logic, views etc including how the app queries the local/remote db, initiate the connection between the local and remote db
- software tests - so It won't break on refactoring
- local and remote debuging toolchain
- some kine of code repo management (Git is hot right now, but always the best choice)