• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: whether to use core data...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: whether to use core data...


  • Subject: Re: whether to use core data...
  • From: Colin Howarth <email@hidden>
  • Date: Sat, 3 Oct 2009 22:10:33 +0200

On 3 Oct, 2009, at 18:12, Izidor Jerebic wrote:

Extremely simplified way of describing CoreData is "easy to use database". So if you have something like a personal library application with list of books, CDs, DVDs etc. that can go into 1000s of items and application has GUI for searching, this would be natural choice for CoreData.


But not all persistent data is good choice for CoreData. If your application has few small objects (e.g. less than 100, each smaller than 10KB), and is using all of them (no searching), then simply persisting them with NSCoding protocol to a document file is probably good solution.

Hmmm, thanks for pointing that out. Although, I liked the undo idea...


--colin _______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >whether to use core data... (From: Colin Howarth <email@hidden>)
 >Re: whether to use core data... (From: Izidor Jerebic <email@hidden>)

  • Prev by Date: Re: whether to use core data...
  • Next by Date: Re: NSPasteboard -> NSTextView
  • Previous by thread: Re: whether to use core data...
  • Next by thread: Re: whether to use core data...
  • Index(es):
    • Date
    • Thread