Core Data vs SQLite 3 [closed]

by

Although Core Data is a descendant of Apple’s Enterprise Object Framework, an object-relational mapper (ORM) that was/is tightly tied to a relational backend, Core Data is not an ORM. It is, in fact, an object graph management framework. It manages a potentially very large graph of object instances, allowing an app to work with a graph that would not entirely fit into memory by faulting objects in and out of memory as necessary. Core Data also manages constraints on properties and relationships and maintains reference integrity (e.g. keeping forward and backward links consistent when objects are added/removed to/from a relationship). Core Data is thus an ideal framework for building the “model” component of an MVC architecture.

To implement its graph management, Core Data happens to use SQLite as a disk store. It could have been implemented using a different relational database or even a non-relational database such as CouchDB. As others have pointed out, Core Data can also use XML or a binary format or a user-written atomic format as a backend (though these options require that the entire object graph fit into memory). If you’re interested in how Core Data is implemented on an SQLite backend, you might want to check out OmniGroup’s OmniDataObjects framework, an open source implementation of a subset of the Core Data API. The BaseTen framework is also an implementation of the Core Data API using PostgreSQL as a backend.

Because Core Data is not intended to be an ORM for SQLite, it cannot read arbitrary SQLite schema. Conversely, you should not rely on being able to read Core Data’s SQLite data stores with other SQLite tools; the schema is an implementation detail that may change.

Thus, there is not really any conflict between using Core Data or SQLite directly. If you want a relational database, use SQLite (directly or via one of the Objective-C wrappers such as FMDB), or a relational database server. However, you may still want to learn Core Data for use as an object graph management framework. In combination with Apple’s controller classes and key-value binding compatible view widgets, you can implement a complete MVC architecture with very little code.

More Related Contents:

  1. Exception thrown in NSOrderedSet generated accessors
  2. Are “EXC_BREAKPOINT (SIGTRAP)” exceptions caused by debugging breakpoints?
  3. Implementing a 30 day time trial [closed]
  4. Cocoa Keyboard Shortcuts in Dialog without an Edit Menu
  5. Using frameworks in a command line tool
  6. Remove Sandboxing
  7. How to save a NSImage as a new file
  8. How can I duplicate, or copy a Core Data Managed Object?
  9. How to launch application and bring it to front using Cocoa api?
  10. Programmatically check if a process is running on Mac
  11. Widget “flip” behavior in Core Animation/Cocoa
  12. Why NSWindow without styleMask:NSTitledWindowMask can not be keyWindow?
  13. How do I copy or move an NSManagedObject from one context to another?
  14. Can I receive a callback whenever an NSPasteboard is written to?
  15. How can I determine the running Mac OS X version programmatically?
  16. How do I draw an NSString at an angle?
  17. Cocoa: What’s the difference between the frame and the bounds?
  18. Formatting NSDate into particular styles for both year, month, day, and hour, minute, seconds
  19. Do you need to create an NSAutoreleasePool within a block in GCD?
  20. How to handle with a default URL scheme
  21. Working with data in iOS Apps (What to choose? NSData, CoreData, sqlite, PList, NSUserDefaults)
  22. Simulate keypress using Swift
  23. Convert String to URL (Why is resulting variable nil)
  24. Get NSTextField contents to scale
  25. check internet connection in cocoa application
  26. NSMutableArray initWithCapacity nuances
  27. using dispatch_sync in Grand Central Dispatch
  28. NSTableView with Plus and Minus buttons
  29. Dropping Files onto Dock Icon in Cocoa
  30. Executing shell commands with NSTask – Objective-C Cocoa

Leave a Comment