Re: migrating CoreData data model doesn't work

2010-05-21 Thread Gustavo Pizano
Hehee,, it makes me remember EOVelocity .. or the Wonder generators from WebObjects On 21.5.2010, at 20:54, Hal Mueller wrote: > 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

Re: migrating CoreData data model doesn't work

2010-05-21 Thread Hal Mueller
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

Re: migrating CoreData data model doesn't work

2010-05-21 Thread Gustavo Pizano
Rainer hello. Have you created once again the ManagedObjects from the model?.. If so and you didn't remove the old ones, Xcode will start complaining A LOT (don't ask me why but it happened to me when I did it), then I realize I had to delete the old MO .m and .h files and generate again form t

migrating CoreData data model doesn't work

2010-05-20 Thread Rainer Standke
Hello, when I select my data model in the xcode project, and then select Design/Data Model/Add Model Version I do get a new bundle in Xcode project, but now copy of the existing datamodel. The bundle, both in Xcode and on the Finder level, is empty. The app does not compile any more. The only