I don’t know of any storage quotas, I’ve seen debug logging fill up the device before the app gets whacked. And some of the games I play have gigs of data.
CoreData has a bit of a curve, but it saves you a lot once you’re used to it. It works at the object level, and just not having to serialize or deserialize your data into SQL columns is a huge win. It also has built in migration strategies so if you rev your schema between app versions, you usually don’t have to write a ton of code to transition your data manually. The design I would recommend (and I’d love to hear if this is what others do) is to use categories to extend the classes that Xcode generates for your CoreData entities. I add methods for every type of query I need. You don’t want to change the generated classes directly, since every time you change an object, Xcode will overwrite any changes you’ve made. On Aug 22, 2014, at 6:07 PM, Carl Hoefs <newsli...@autonomy.caltech.edu> wrote: > > On Aug 22, 2014, at 6:01 PM, Jim Geist <velocity...@rodentia.net> wrote: > >> Can you use CoreData? > > On Aug 22, 2014, at 6:00 PM, Catchall <catch...@rodentia.net> wrote: > >> Is there a reason to not use CoreData? > > Hmm, I guess that’s what CoreData is for, isn’t it? I had heard that it is > pretty difficult to learn, and since I’m used to accessing databases from > C/Linux, my first thought was to go the “easy” route. I’ll look into it. > > Regarding the other portion of my question, are there limitations to how much > storage space can be used on an iPhone? Is the space managed as “first-come > first-served”? > Thx, > -Carl > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
