ios - What are the Best Practices for Cache And Syncing in iPhone -

ios - What are the Best Practices for Cache And Syncing in iPhone -

i looking way cache info on client side, , sync info server info on basis of time stamp, worried way go whether utilize coredata or sqlite.

i know coredata not rdbms , takes in memory finish object space, on other side sqlite much powerful,

what best selection coredata or sqlite.

further in future version (that expected) if server info base of operations undergo changes column added table or deleted reason or updated, how can plan accomplish scalability.

any thoughts much appreciated..

thanks

i've preffered sqlite guess they're both equivalent each other. sqlite much more simple (from experience, junior-level) when need utilize it, stuff fmdb (git it!).

i've been told sqlite > coredata (if wanna create simple). , happen sense same way after having used both. though on other hand, if you're not using fmdb, sqlite painful code with.

scalability? you'd need update app , tables, that's same both choices. again, kinda sense completly sentiment based when sqlite feels easier , more comfortable play with. wether using sql or updating db.

now wanna emphasize before downvoted : it's how sense , not simple fact agrees on. wait more answers. i've used coredata in 2 or 3 different projects, i've used sqlite in way more, maybe i'm used one.

ios objective-c iphone sqlite core-data