Alex Reynolds wrote:
Unfortunately, that simple solution means parting ways with the
naming scheme of the source I'm pulling data from and changing the
naming scheme for all my other entities/classes, too, which I was
hoping to avoid. But thanks to all for the confirmation.
Maybe:
#defi
On Sep 30, 2009, at 1:11 PM, Alex Reynolds wrote:
Unfortunately, that simple solution means parting ways with the
naming scheme of the source I'm pulling data from and changing the
naming scheme for all my other entities/classes, too, which I was
hoping to avoid. But thanks to all for the c
As a general rule, you want to avoid attempting to name classes with
such generic names. It makes you very much more likely to end up with
a class name conflict somewhere, especially in large projects.
Classname prefixes are usually what's used to help ensure there are no
such conflicts.
On Sep 30, 2009, at 4:04 AM, I. Savant wrote:
Whatever the answer, the simple solution is to change your entity's
name.
Unfortunately, that simple solution means parting ways with the naming
scheme of the source I'm pulling data from and changing the naming
scheme for all my other entiti
On Sep 30, 2009, at 3:53 AM, Alex Reynolds wrote:
After I added an Entity called "Object", I get the following message
when executing my application on the iPhone:
objc[4219]: Class Object is implemented in both /usr/lib/
libobjc.A.dylib and /var/mobile/Applications/BFDFC14C-DB60-44BB-8118-
This doesn't sound directly like a Core Data problem as such. Note how
the message mentions nothing about entities, but instead is
complaining you've got two separate classes with the same name. So you
should be fine to have an entity named "Object" but don't make the
classname that. Call i
After I added an Entity called "Object", I get the following message
when executing my application on the iPhone:
objc[4219]: Class Object is implemented in both /usr/lib/
libobjc.A.dylib and /var/mobile/Applications/BFDFC14C-DB60-44BB-8118-
D2AAB39E2EE6/MyApp.app/MyApp. One of the two will b
