Re: Core Data migration and non-optional transient relationships
Re: Core Data migration and non-optional transient relationships
- Subject: Re: Core Data migration and non-optional transient relationships
- From: Dave Fernandes <email@hidden>
- Date: Tue, 20 May 2014 13:28:28 -0400
During migration you have a bare NSManagedObject and not your custom subclass. So any custom code has to be in a migration policy.
Sent from my iPhone
> On May 20, 2014, at 12:07 PM, Mike Abdullah <email@hidden> wrote:
>
>
>> On 20 May 2014, at 15:21, Sean McBride <email@hidden> wrote:
>>
>> Hi all,
>>
>> Doing a Core Data migration (not the lightweight kind) I hit an error at the end:
>>
>> "foo is a required value."
>>
>> the 'foo' relationship it complains about is transient and so not present in the store. Normally, I recreate the relationship in awakeFromFetch, but it doesn't seem to call that during migration. As a test I made the relationship optional, then it no longer complains.
>>
>> This seems to mean that transient relationships must always be optional?! At least if you ever want to migrate. That seems odd. Am I missing something here?
>
> How about -awakeFromInsert? During a migration, new objects are being created, based on the existing ones. Thus -awakeFromInsert gets called on them rather than -awakeFromFetch.
>
>
> _______________________________________________
>
> 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
_______________________________________________
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