title: Edges records not showing up in OrientDB
body: <p>I've discovered recently about OrientDB and I've been playing a little with this tool these past few weeks. However, I noticed today that something seemed to be wrong whenever I added an edge between two vertices. The edge record is not present if I make a query such as <code>SELECT FROM E</code>, this just returns an empty set. In spite of this, it is possible to see the relationship as a property in the nodes, and queries like <code>SELECT IN() FROM V</code> do work.</p>
  
  <p>This poses an issue; if I can't access directly the edge record, I can't modify it with more properties, or even if I could, I wouldn't be able to see the changes made. I thought this could be a design decision for some reason but the GratefulDeadConcerts example database doesn't seem to have this problem.</p>
  
  <p>I'll illustrate my question with an example:</p>
  
  <p>Let's create a graph database in OrientDB from scratch and name it "Test". We'll create a couple of vertices:</p>
  
  <pre><code>CREATE VERTEX SET TEST=123
  CREATE VERTEX SET TEST=456
  </code></pre>
  
  <p>Let's assume the @rid of these nodes are #9:0 and #9:1 respectively, as we haven't changed anything from the default settings. Let's create an edge between them:</p>
  
  <pre><code>CREATE EDGE FROM #9:0 TO #9:1
  </code></pre>
  
  <p>Now, let's take a look at the output of the query <code>SELECT FROM V</code>:</p>
  
  <pre><code>orientdb {Test}&gt; SELECT FROM V
  
  ----+----+----+----+----
  #   |@RID|TEST|out_|in_
  ----+----+----+----+----
  0   |#9:0|123 |#9:1|null
  1   |#9:1|456 |null|#9:0
  ----+----+----+----+----
  
  2 item(s) found. Query executed in 0.005 sec(s).
  </code></pre>
  
  <p>Everything looks right so far. However, the output of the query <code>SELECT FROM E</code> is simply <code>0 item(s) found. Query executed in 0.016 sec(s).</code>. If we execute <code>SELECT IN() FROM V</code> we get the following:</p>
  
  <pre><code>orientdb {Test}&gt; SELECT IN() FROM V
  
  ----+-----+----
  #   |@RID |IN
  ----+-----+----
  0   |#-2:1|[0]
  1   |#-2:2|[1]
  ----+-----+----
  
  2 item(s) found. Query executed in 0.005 sec(s).
  </code></pre>
  
  <p>From this, I assume that the edges are created in cluster number -2, even if the default cluster for the class E is 10, and I haven't added any other clusters. I suspect this has something to do with the problem, but I'm not sure how to fix it. I have tried adding new clusters to the class E and creating the edges in this new cluster, but to no avail, I keep getting the exact same result.</p>
  
  <p>So my question is, how do I make edges records show up in OrientDB?</p>
  
  <p>I'm using OrientDB Community 1.7-RC2 and have tried this in two different machines, one Windows 7 and another one Debian Wheezy.</p>