• 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: migrating CoreData data model doesn't work
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: migrating CoreData data model doesn't work


  • Subject: Re: migrating CoreData data model doesn't work
  • From: Hal Mueller <email@hidden>
  • Date: Fri, 21 May 2010 11:54:53 -0700

MOGenerator (from Wolf Rentzsch) is one solution to this problem. It uses one file for human-written custom code, another file for machine-generated boilerplate code.

http://github.com/rentzsch/mogenerator

Hal

On May 21, 2010, at 4:53 AM, Gustavo Pizano wrote:

> Now if you have custom methods in your MO's then what I do is that I don't delete, or create a new one, but simply add by had the new(s) attributes I set in the new model version. Im pretty sure there i another way to do this,

_______________________________________________

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

  • Follow-Ups:
    • Re: migrating CoreData data model doesn't work
      • From: Gustavo Pizano <email@hidden>
References: 
 >migrating CoreData data model doesn't work (From: Rainer Standke <email@hidden>)
 >Re: migrating CoreData data model doesn't work (From: Gustavo Pizano <email@hidden>)

  • Prev by Date: Re: NSXMLParser initWIthData - Encoding?
  • Next by Date: Getting TextEdit to Recognise UTF-8 Output
  • Previous by thread: Re: migrating CoreData data model doesn't work
  • Next by thread: Re: migrating CoreData data model doesn't work
  • Index(es):
    • Date
    • Thread