@Scott: The article is part of an ebook by O'Reilly called Graph Databases. It's available for free from http://neo4j.com/books/graph-databases/
I think you might be misunderstanding my objective. Person and Contact both extend V, and each contains appropriate properties for their respective objects. The example is overly simplified (and I wouldn't actually do this in practice), but the question is about the edges and whether it's better to have multiple edge classes or one edge class that has a property that identifies the "type" of contact. I think both approaches will work, I'm just looking for input on the pros/cons of each. --Eric On Friday, July 10, 2015 at 1:54:15 PM UTC-5, scott molinari wrote: > > Ok, but phone and email aren't really types of edges you would normally > create. They don't indicate a relation. In OrientDB, you'd store the email > and phone as properties of the vertex or document class. An edge would be > something like "isA". Person->isA->Contact. Granted, I have to admit, my > knowledge of ODB is limited, but from everything I've read and seen thus > far, you just wouldn't create edges like that. > > Can you post a link to the article about Neo4j you mentioned above? > > 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.
