On Nov 30, 2011, at 2:39 PM, Jerry Krinock wrote: > > On 2011 Nov 30, at 12:09, Alex Kac wrote: > >> a cascade delete from the parent object and a nullify from the inverse > > that should work
And it does…except when it doesn't. To put it in perspective we have a few hundred thousand users and I've only seen this twice. Now its possible there is something we're doing causing this (we're double checking all of our code). > >> If I open the database file just to check, I see that the entity object is >> being referred to, but again it does not exist anymore. > > Do you mean that the value of Z<FOO> in a certain row is a number which does > not exist as a primary key Z_PK in the table of the destination entity? Yup. > > I've never seen that happen! Your code probably didn't have the bug ours probably does :) I personally suspect its somewhere we are calling setPrimitiveX and not handling the cascade ourselves properly. Its not my code so I'm not sure, but that's what I suspect. But even if we do find what causes that problem I still want some way to fix it for anyone it does occur to._______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
