title: Does every Core Data Relationship have to have an Inverse?
body: <p>Let's say I have two Entity classes: <code>SocialApp</code> and <code>SocialAppType</code></p>
  <p>In <code>SocialApp</code> I have one Attribute: <code>appURL</code> and one Relationship: <code>type</code>.</p>
  <p>In <code>SocialAppType</code> I have three Attributes: <code>baseURL</code>, <code>name</code> and <code>favicon</code>.</p>
  <p>The destination of the <code>SocialApp</code> relationship <code>type</code> is a single record in <code>SocialAppType</code>.</p>
  <p>As an example, for multiple Flickr accounts, there would be a number of <code>SocialApp</code> records, with each record holding a link to a person's account. There would be one <code>SocialAppType</code> record for the &quot;Flickr&quot; type, that all <code>SocialApp</code> records would point to.</p>
  <p>When I build an application with this schema, I get a warning that there is no inverse relationship between <code>SocialAppType</code> and <code>SocialApp</code>.</p>
  <pre><code> /Users/username/Developer/objc/TestApp/TestApp.xcdatamodel:SocialApp.type: warning: SocialApp.type -- relationship does not have an inverse
  </code></pre>
  <p>Do I need an inverse, and why?</p>