title: Using a NSFetchedRequest or a NSSortedDescriptior on a to-many property?
body: <p>Say we have a entity <code>Company</code> that has a to-many relationship to the <code>Employee</code> entity via the <code>employees</code>.</p>
  
  <p>If I want to find the last created <code>Employee</code> (assume <code>Employee</code> has a <code>NSDate</code> property <code>created</code>), which of these two approaches is better?</p>
  
  <ul>
  <li>create a <code>NSFetchRequest</code> on <code>Employee</code>, restricted to <code>"company == %@", someCompany</code>, sort by <code>created</code>, and set the <code>fetchLimit</code> to 1</li>
  <li>or use <code>sortedArrayUsingDescriptors:</code> on <code>someCompany.employees</code> with a <code>NSSortDescriptor</code> on <code>created</code> and take the first?</li>
  </ul>
  
  <p>While the second approach seems more straight forwards, I'm concerned about the actual processing. The first approach would allow the system to tailor a custom query, while the second does some in-memory sorting? I guess it boils down to whether to-many relationships are lazy or not.</p>