• 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: Best Way To Lookup From a Huge Table
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best Way To Lookup From a Huge Table


  • Subject: Re: Best Way To Lookup From a Huge Table
  • From: Chris Hanson <email@hidden>
  • Date: Fri, 14 Mar 2008 18:15:51 -0700

On Mar 14, 2008, at 5:55 PM, John Stiles wrote:

Frankly, if it's just a table of 100,000 NSNumbers pointing to 8- character strings, CoreData seems a little excessive to me. The table can live in RAM and it shouldn't cause any problem.

Why does it seem excessive?

Once you understand its concepts, Core Data is quite easy to use and it's not a heavyweight framework, especially for something like this where you just have a couple related entities that you want to fetch from a read-only store at runtime. It's great at persistence as well as object-graph management (to refer to another thread).

  -- Chris

_______________________________________________

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: 
 >Best Way To Lookup From a Huge Table (From: Karan Lyons <email@hidden>)
 >Re: Best Way To Lookup From a Huge Table (From: Chris Hanson <email@hidden>)
 >Re: Best Way To Lookup From a Huge Table (From: John Stiles <email@hidden>)

  • Prev by Date: Re: export unit tests results
  • Next by Date: previous value of NSControl
  • Previous by thread: Re: Best Way To Lookup From a Huge Table
  • Next by thread: Re: Best Way To Lookup From a Huge Table
  • Index(es):
    • Date
    • Thread