I have an iphone app with tons of coredata data. I am trying to implement a full backup method where i can get all of the data from the app and throw it to a webserver. I prefer to use json data for this format. Is there an easy way to dump all of the application data out of the system? or a method for backing up the data structures directly from in an app?
You could just upload the persistent store file itself. That would grab everything.
We ended up building something cool for this by grabbing the sqlite file and a web service. Everything seems to be good as long as connection is not broken. Let me know any questions on this in the future
Related
looking to make an iOS app where I can take a picture and then send it to a my own searchable database, website or wiki. What would be the easiest service to do this (I can do the iOS programming its just I don't know about the other side of it).
The easiest option would be to use CoreData. If you don't know about CoreData, Apple has a very comprehensive set of documentation located here: https://developer.apple.com/library/ios/#documentation/DataManagement/Conceptual/iPhoneCoreData01/Introduction/Introduction.html
Using CD, you can save the images as NSData in the persistent store, and then turn them back into images as you fetch them from the store. The most common implementation of CoreData uses SQLite as the backing store.
I am not quite sure how to answer your question without building a db for you. If you are just looking for resources on how to build a db, check out this stackoverflow question
I think iphone apps have a database somewhere, and when a user updates data in application it contacts the server and gets an xml from the database and parses it? Am i right? I want to be able to create apps that tranfer data through the internet but i dont know how. Is xml the correct way to do it? If yes, then how can i convert a SQLite saved to my PC into a xml file and send it to iphone?
XML is often used for transferring data, and many iOS-based apps do use SQLite for data storage. That said, there's not a single "correct" format for transferring or storing data -- do what works best for your situation.
I am developing my first iPhone application and currently considering whether to deploy the app packaged with data, instead of calling upon a web service for the info. The obvious benefits are for those situations where you have a poor/non-existent connection and i could easily write something that could update the client data periodically from within the app.
What i am not sure about is how to store the data - sqlite, core data, plist or iphone file structure - Simply because i dont want someone unzipping the deployed application and getting their hands on the raw data.
Is this actually feasable? or is pretty much everything accessible once its deployed as an app?
You cannot stop somebody from accessing the data stored on the device, independently if you use sqlite, core data, plist or iphone file structure. At least not within reasonable means.
What you can do rather easily is to make the data useless for unauthorized access. In other words: encrypt it.
If what format you store the encrypted data then depends on the app needs.
This is pretty tough to do. The easiest way to do this would be by using the Xcode Organizer panel and then looking at the applications that you have installed. If it is one of your applications (matching your dev credentials) then Xcode will give you the option to download the application's sandboxed folders (docs, temp, etc).
From memory, you cannot do this to another application that doesn't belong to you. So in short you are safe to include data in your app. Honestly though, if someone wants to get to that data, they always will given enough time and resources (thats my opinion about all security).
I am in iPhone Application Development since last few months only..
So, I have working with some applications, and in all of the applications i used to follow the SOAP web service methods to get the data in my applications.
I have heard something on SQLite, but have lots of confusion regarding important of it.
So, if anybody can explain or just give me a hint regarding on SQLite will highly appreciated.
Thanks in advance...
SQLite is a database if you want to have data stored you can use it. You use web service because the data is not stored locally. SQLite allows you to store data locally.
http://dblog.com.au/iphone-development-tutorials/iphone-sdk-tutorial-reading-data-from-a-sqlite-database/
http://www.mobileorchard.com/iphone-sqlite-tutorials-and-libraries/
In a nutshell SQLite is a library used to provide local database access to your iPhone app.
http://www.sqlite.org/
I'm currently in the process of deciding whether or not to use Core Data for managing the data in my iphone application.
The application involves putting together a fairly sizeable library of content which needs to be localised and has a fair few relationships. One benefit I thought of using core data would be that I could perhaps build a desktop client for managing the data of the application, then package the resulting file with the iPhone app to use as its content database.
With my fairly limited knowledge of Core Data I wanted to know if this is possible? Are their any best-practices people can point me in the direction of?
This is basically a dupe of this question:
Provide Base Data for Core Data Application?
Short answer is - YES. I've done it, Apple does it. Works well.
Core Data defines the interface for interacting with the database, not the storage itself. You can use XML, Binary, or SQLite as the storage file. If you want a quick-and-dirty solution, you could use a basic SQLite application such as Menial's Bases to create a database. You can then add this to your XCode project for use by the iPhone. If you intend for the desktop client to be used by your iPhone customers, you can can use much of the same Core Data code from your iPhone project.
Core Data is now included starting a SDK 3.0.