Okay that's perfect. Thanks for the clarification. Definitely need the documents to be updated to help understand the duality of the database and the differences between the two modes. Many times the tutorials/videos will describe an approach and its not clear if they are talking about a vertex or document. The documents elude to vertices and documents being synonymous, but that's clearly not the case in the way the database treats things.
On Friday, March 20, 2015 at 4:24:40 PM UTC-4, Colin wrote: > > Hi Gregory, > > We're working on the documentation every day to improve it. However, what > might be confusing, at first, is that OrientDB is both a document and a > graph database. It's a true multi-model database. > > When treating a class as a document, you can create links manually to > other documents, and you're right, the direction is one way. The target > document knows nothing about the originator. > > However, when treating classes as a vertex of a graph (class extends V) > and you create edges between them, those relationships are absolutely > bi-directional, and you can traverse them in both directions. > > When creating links for a document, you must handle the relationships > yourself. > > When creating links (edges) for vertices, the system will manage them for > you. As an example, if you delete an edge between two vertices, the system > will remove the attachments on both vertices. > > Hope that helps a bit. > > -Colin > > Orient Technologies > > The Company behind OrientDB > > On Friday, March 20, 2015 at 12:44:10 PM UTC-5, Gregory Pierce wrote: >> >> I'm evaluating OrientDB for some particular use cases and while overall >> the database seems to be very cool (though somewhat confusing in its >> descriptions as it tries to use the terminology for both document and graph >> databases... pick one set of terms and only use those), there seem to be >> some unclear bits. >> >> One of the things that I'm having an issue with for OrientDB is that >> vertices appear to have a direction. Company->Employs->Employee. However an >> of these vertex relationships are really directionless. To say that a >> company employs an employee is to also say that an employee is employed_by >> a company. >> >> With the query syntax it appears that to model things properly I would >> need to create the relationship in each direction when it seems to be >> something that would make sense to work in both directions. >> > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
