• 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: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment?


  • Subject: Re: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment?
  • From: Jerry Krinock <email@hidden>
  • Date: Tue, 7 Sep 2010 14:55:15 -0700

On 2010 Sep 07, at 12:15, Quincey Morris wrote:

> On Sep 7, 2010, at 11:26, Jerry Krinock wrote:
>
>> 4.  I cannot find the workaround mentioned in the warning in Core Data's 10.6 Release Notes.
>
> Does this describe and/or provide a solution for your problem?
>
>    http://developer.apple.com/mac/library/releasenotes/Cocoa/MigrationCrashBuild106Run105/index.html

Wow, that's quite a document there, chief.  It says that, building on Mac OS 10.6, Xcode creates an expression which invokes an undocumented NSMigrationManager method which does not exist in Mac OS X v10.5.  And the workaround is: They give you the code for the method and tell you to stitch it into the runtime.

So I looked more closely at that mapping model.  It has 19 entities and 9 to-one|to-many relationships.  By that I mean it has 9 of these guys:

   <----->>

The auto-generated expression for migrating 8 of them involves

  destinationInstancesForEntityMappingNamed:sourceInstances:

But, inexplicably, for the one that generates the error, the expression instead involves the new 10.6 method:

  destinationInstancesForSourceRelationshipNamed:sourceInstances:

Well, anyhow, it turns out that the stores which I'd successfully migrated earlier today didn't have any objects of that entity, so that's why they worked.  With a more contrived data set, it crashed as expected.

So, the answer is YES and YES, and thanks Quincey.  Assuming the workaround works, I'm done.

But I'd still like to know how I built a half dozen mapping models during this calendar year, and each migrated a half dozen or more <---->> relationships, and they all auto-generated expressions which invoked the old method, and now all of a sudden one relationship in one mapping model requires this new method.

_______________________________________________

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:
    • Patching implementation in +load. Was: …Mapping Model : Spurious Warning
      • From: Jerry Krinock <email@hidden>
    • Re: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment?
      • From: Quincey Morris <email@hidden>
References: 
 >Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment? (From: Jerry Krinock <email@hidden>)
 >Re: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment? (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: recalling the original view height
  • Next by Date: Re: UIViewController: not receiving motion events
  • Previous by thread: Re: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment?
  • Next by thread: Re: Compiling Core Data Mapping Model : Spurious Warning re 10.5 Deployment?
  • Index(es):
    • Date
    • Thread