You see, that is the problem with me. ODB says, "Use the graph API, because then the graph relationships are handled automatically for you:" Well, that seems to be true, but only to a point. When you say I have to still think about relationships being stored in some list and that vertexes are actually oblivious to how they relate to other vertexes, well, to me, that isn't a graph database. That is a document database with edges stored in a collection of documents.
In other words, the fact that is actually what is happening in the background, shouldn't matter at all. The graph database should abstract the relationships to be meaningful, both from a graph usage perspective and a database operational perspective. Scott -- --- 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.
