title: What's the right way to add methods and properties to a CoreData entity? Subclass them?
body: <p>I am trying to add additional properties and methods to entity classes that I'd like to decouple from the automatically generated <code>NSManagedObject</code> subclasses.</p>
  
  <p>The class definition files that are automatically generated by Core Data are very helpful, and I like being able to change the data scheme and regenerate them quickly, without fear of wiping out my extensions, so subclassing feels like the right overall approach.</p>
  
  <p>But when I do this (for example, subclass of <code>Person</code> called <code>MyPerson</code>) — that seems to function, but leads to confusion when using tools like MagicalRecord that are expecting the entity name to match the class name. (i.e. <code>[Person findAll]</code> works but <code>[MyPerson findAll]</code> fails because it finds no entity called <code>MyPerson</code>.)</p>
  
  <p>Feeling like I'm banging my head against the wall too much; what is the right design pattern to pursue here? Thanks for the help.</p>