Re: Core Data: transient attributes require bogus type to quiet compiler?
Re: Core Data: transient attributes require bogus type to quiet compiler?
- Subject: Re: Core Data: transient attributes require bogus type to quiet compiler?
- From: Matthew Firlik <email@hidden>
- Date: Wed, 13 Jul 2005 16:25:42 -0700
On Jul 13, 2005, at 3:32 PM, Michael McCracken wrote:
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
The warning emitted from the MOM compiler when using transient
attributes with undefined types is a bug. We have it listed in our
bug reporting system already and will address it as soon as
possible. Unfortunately, there is no workaround at the moment.
However, that particular warning is harmless (other than the
pollution of the build log and a false increment of the warning count
in Xcode), so it can be safely ignored.
- matthew
= = = = =
Matthew Firlik
Manager, Core Data
email@hidden
_______________________________________________
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