Is there a reason not to use the same attribute names in Core Data entities?

Is there a reason not to use the same attribute names in Core Data entities?

I have a data model with several entities and some of those entities share attributes that naturally have the same name. Is there any reason to add detail to those names to help distinguish them or will I only ever use them in their fully qualified formats?

For example, if my model had library, librarian, book, borrower and author entities all those entities might have an attribute called "name". If that attribute will almost always be referred to in a qualified format (e.g. or there'd be no reason to choose different names but if there's any chance of confusion I would be inclined to make the attribute names unique (e.g. libraryName, librarianName, etc).

I apologise for such a basic question but I'm new to Core Data and not yet familiar with how these attribute names are used.

NSBezierPath / Line Intersection / flatten


getting the path of a application at runtime + cocoa
Using the same attribute name, i.e.

Cocoa application architecture on Mac OS X
name for both Person and Pet entities is fine..
Garbage collection of Core Foundation objects
The case where this is not ok is the case Pet inherits from person — in this case the managed object model compiler will generate an error about conflicting property names when it compiles your model file..
get size of nswindow

How do I update a constraint on my CALayer?

88 out of 100 based on 78 user ratings 478 reviews