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
On 20 May 2014, at 15:21, Sean McBride s...@rogue-research.com 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.
On 2014 May 20, at 07:21, Sean McBride s...@rogue-research.com wrote:
As a test I made the relationship optional, then it no longer complains.
Consider leaving it that way, Sean. The only effect I’ve ever had from setting
Core Data properties to be non-optional is the creation of mysterious
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 mabdul...@karelia.com wrote:
On 20 May 2014, at 15:21, Sean McBride s...@rogue-research.com
