On 21 Oct 2011, at 6:17 AM, Jerry Krinock wrote:
> On 2011 Oct 20, at 12:03, Fritz Anderson wrote:
>
>> Does it in fact not work? Or is there something else I should be frobbing?
>
> I think that the lightweight migration you described should work, and there
> is something else you should be frobbing.
I understand your answer to mean that the problem may come from a bug in
apparently-unrelated code, which was exposed by instituting the migration, and
I haven't supplied enough information to debug this specific problem.
Acknowledged.
What I meant by "something else I should be frobbing" is whether there was an
additional step I am supposed to be taking in building my Core Data stack.
processPendingChanges? save:? These seem to be gratuitous. I'd experiment, but
I have to be away from the project till Monday.
I still hope that someone can come up with guidance on where to look. The
migration is the _only_ change between working and not-working. The managed
object comes back as a fault _immediately_ after the fetch, and accessing any
attribute raises an exception. (Incidentally, -isDeleted is NO.)
I wonder if this is familiar to anyone?
— F
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
