Skip navigation.
 
mlRe: -[NSManagedObjectContext save:] fails but gives no NSError
FROM : Chris Hanson
DATE : Sat Nov 24 07:38:51 2007

On Nov 23, 2007, at 9:47 PM, Jerry Krinock wrote:

> What I am sure about is that, as per the code in my original post, 
> although I was giving -save: an NSError**, it was returning NO, my 
> store file on the disk was not touched, and the NSError* was nil.
>
> If it ever happens again, I'll test more closely and let you know.


Is there any chance you can do a diff between what you have in your 
SCM system and what you have now, that works, and file a bug 
describing what you were doing previously?

You should *never* rely on an output NSError argument being set to a 
non-nil as a sign of an error; you should *always* check the actual 
result of the method or function, and only look at the returned 
NSError after that.  However, it's still a serious bug for any API 
that takes an output NSError parameter to fail without returning a 
corresponding NSError, and it would be worth pursuing.

Thanks!

  -- Chris

Related mailsAuthorDate
ml-[NSManagedObjectContext save:] fails but gives no NSError Jerry Krinock Nov 22, 04:34
mlRe: -[NSManagedObjectContext save:] fails but gives no NSError Jerry Krinock Nov 23, 18:24
mlRe: -[NSManagedObjectContext save:] fails but gives no NSError mmalc crawford Nov 23, 23:46
mlRe: -[NSManagedObjectContext save:] fails but gives no NSError Jerry Krinock Nov 24, 06:47
mlRe: -[NSManagedObjectContext save:] fails but gives no NSError Chris Hanson Nov 24, 07:38
mlRe: -[NSManagedObjectContext save:] fails but gives no NSError Jerry Krinock Dec 5, 02:22