• 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: [Leopard] Core Data model versioning vs. NSPersistentDocument
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Leopard] Core Data model versioning vs. NSPersistentDocument


  • Subject: Re: [Leopard] Core Data model versioning vs. NSPersistentDocument
  • From: mmalc crawford <email@hidden>
  • Date: Wed, 31 Oct 2007 19:23:59 -0700


On Oct 31, 2007, at 4:00 PM, Pierre Bernard wrote:

Does NSPersistentDocument handle versioning issues or do I need to hook into document loading to call the migration manager myself?
What is the recommended approach for using the migration manager within the NSDocument architecture?


It's just as described here <http://developer.apple.com/documentation/Cocoa/Conceptual/CoreDataVersioning/Articles/vmInitiating.html >.

mmalc

_______________________________________________

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: 
 >[Leopard] Core Data model versioning vs. NSPersistentDocument (From: Pierre Bernard <email@hidden>)

  • Prev by Date: Re: [Moderator] Leopard documentation update now available online
  • Next by Date: Re: Garbage collection, core data, and tight loops
  • Previous by thread: [Leopard] Core Data model versioning vs. NSPersistentDocument
  • Next by thread: NSBitmapImageRep byte/color component ordering
  • Index(es):
    • Date
    • Thread