• 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: Newbie Help understanding Core Data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Newbie Help understanding Core Data


  • Subject: Re: Newbie Help understanding Core Data
  • From: SA Dev <email@hidden>
  • Date: Thu, 28 Jul 2005 08:46:45 -0400


On Jul 27, 2005, at 4:56 PM, Charilaos Skiadas wrote:

In sort, I see no reason for any application that handles a lot of data to not use Core Data for that.

Actually, there are plenty of reasons. :-)

1 - No file package support - Search for the previous thread (between myself and mmalc) where the documentation states you can do this, but there is a 'known issue' that makes this basically broken - some applications deal with a lot of 'contained' media files that the user should be able to get at without the application's help or if the data file is corrupted.

2 - No true multi-user support - Try creating the next Great Accounting System and telling your users it only supports one concurrent user ... good luck with your sales to anything but "mom and pop shops".

3 - Backward compatibility - There are still plenty of Panther and even Jaguar users out there. Heck, I was just e-mailed a few days ago asking if there was a version of one of my apps for 10.1, and a few days before that, 9.x.

4 - K.I.S.S. ("keep-it-simple-stupid") Principle - Using Core Data for something ultra simple (like a simple list of items with one or two properties each) is like swatting a fly with an aircraft carrier.*** When a simple dictionary or array's read/write to/from file methods will work just fine, Core Data is a bit much, even if that list is several thousand lines long, if it's just a few properties that are all listed in a flat table, their values are going to be retrieved anyway ...

*** - of course this depends heavily on your application, but it can certainly be true in a number of scenarios. Also, it's not to say Core Data is a big slow beast, just that for simpler data models, it can be overkill.


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Newbie Help understanding Core Data
      • From: Charilaos Skiadas <email@hidden>
References: 
 >Newbie Help understanding Core Data (From: Vince Ackerman <email@hidden>)
 >Re: Newbie Help understanding Core Data (From: Charilaos Skiadas <email@hidden>)

  • Prev by Date: ABPeoplePickerView - Getting the selected property
  • Next by Date: Running remote commands through sudo/sec framework?
  • Previous by thread: Re: Newbie Help understanding Core Data
  • Next by thread: Re: Newbie Help understanding Core Data
  • Index(es):
    • Date
    • Thread