Core Data: transient attributes require bogus type to quiet compiler?
Core Data: transient attributes require bogus type to quiet compiler?
- Subject: Core Data: transient attributes require bogus type to quiet compiler?
- From: Michael McCracken <email@hidden>
- Date: Wed, 13 Jul 2005 15:32:11 -0700
Hi, I have an attribute for an entity that I am generating it in code
and don't need to store it for each entity, so it's marked as
transient. I didn't specify a type for the attribute because it isn't
one of the standard types and I'm not storing it. This is on the
advice of the following:
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdNSAttributes.html
specifically:
"You can, however, specify the type of a transient property as being
undefined, since Core Data does not need to store and retrieve these
properties."
But when I do this, I get a compiler (momc) warning that I have a
"transient attribute with undefined type" - what's the point of this
warning? Is there some advantage to lying to the data model about what
type I'll be returning in my subclass for this attribute, or am I
missing some larger point?
Thanks,
-mike
--
Michael McCracken
UCSD CSE PhD Candidate
research: http://www.cse.ucsd.edu/~mmccrack/
misc: http://michael-mccracken.net/blog/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden