title: neo4j: one-directional / two-directional relationships?
body: <p>So I looked into neo4j, and I may be using it in an upcoming project since its data model might fit my project very well. I looked through the docs but I still need an answer to this question:</p>
  
  <p><strong>Can I set relationships to be one-directional?</strong></p>
  
  <p>It seems that the neo4j people like movies so let's continue with that. If I have a graph like this:</p>
  
  <pre><code>Actor A -&gt; [:Acts in] -&gt; Movie B
  </code></pre>
  
  <p>then direction is obvious, because the nodes are different types.</p>
  
  <p>But I like horror movies so...</p>
  
  <pre><code>Person A -&gt; [:wants_to_kill] -&gt; Person B
  </code></pre>
  
  <p>I need this relationship to be one-directional so if I query "Who does Person A want to kill?" I get Person B, if I query "Who does Person B want to kill?" I get nothing.</p>
  
  <p><strong>Sometimes I still need relationships to be two directional</strong></p>
  
  <p>Like:</p>
  
  <pre><code>Person A &lt;-[:has_met] -&gt; Person B
  </code></pre>
  
  <p>...which is obvious.</p>
  
  <p><strong>documentation says:</strong></p>
  
  <pre><code>Relationships are equally well traversed in either direction. This means that there is
  no need to add duplicate relationships in the opposite direction (with regard to 
  traversal or performance).
  
  While relationships always have a direction, you can ignore the direction where it is 
  not useful in your application.
  </code></pre>
  
  <p>So docs say, relationships by default have an direction and I can ignore that if I wish.</p>
  
  <p>Now this is where things get complicated:</p>
  
  <p>Consider the following graph (and note the arrows)</p>
  
  <pre><code>Person A &lt;- [:wants_to_kill] -&gt; Person B
  Person B -&gt; [:wants_to_kill] -&gt; Person C
  Person C -&gt; [:wants_to_kill] -&gt; Person A
  </code></pre>
  
  <p>If I ignore the Directions for all <code>[:wants_to_kill]</code> I get false results
  for "Who does Person A / C want to kill?"
  If I knew which ones I had to ignore, I would not do the query.</p>
  
  <p>So can I somehow set relationships to be two-directional (when creating them), or should I model this with two relationships (between Person A &amp; B)?</p>