• 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: Core Data: How best to create a data model for tracking changes to related objects?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data: How best to create a data model for tracking changes to related objects?


  • Subject: Re: Core Data: How best to create a data model for tracking changes to related objects?
  • From: "Michael Ströck" <email@hidden>
  • Date: Mon, 12 Feb 2007 10:07:22 +0100

But then again, like Scott Stevenson wrote, 10.000 items is nothing
worry about.

Just for reference, I once slapped together a special-purpose, unoptimized CoreData application in a single afternoon. I needed an UI for rather involved hand-processing over 250-thousand items of stock-market data. I let the import-job run overnight (so I have no idea how long it took) and was half-expecting things to not work at all. Thankfully, the actual processing was done by two interns, but performance was very bearable on first-generation Intel Mac.

--
Michael Ströck
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: 
 >Re: Core Data: How best to create a data model for tracking changes to related objects? (From: René v Amerongen <email@hidden>)

  • Prev by Date: Re: [CORE DATA] is it safe to modify/delete a managed object during its validation?
  • Next by Date: Running daemon services.
  • Previous by thread: Re: Core Data: How best to create a data model for tracking changes to related objects?
  • Next by thread: Running daemon services.
  • Index(es):
    • Date
    • Thread