I know this is probably by design but I thought I’d check with the community first.
How come when I have an NSManagedObject that’s new, its NSNumber properties return 0? I want them to be nil til they’ve been set.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know this is probably by design but I thought I’d check with the community first.
How come when I have an NSManagedObject that’s new, its NSNumber properties return 0? I want them to be nil til they’ve been set.
Did you just forget to uncheck the
defaultvalue option?The NSManagedObject will return nil for that attribute if
defaultis unchecked and the attribute was never set. At least that’s what happens in my app.