Thanks Colin. That is what I was thinking.
I love the cluster/class with inheritance concept for sure. I also love the linking and graph relational capabilities in ODB. However, I feel the cluster/class concept is mixing application domain concerns with database data locality concerns, which, on face value, don't really necessarily always have anything to do with one another. This is especially tricky, when this class/cluster concept is also given to a tenant user of the database in a multi-tenant situation. The user has no idea what damage they might be causing from a data locality standpoint, by improperly setting up classes, which won't scale well and it really shouldn't be up to any user to have to consider data locality either. I guess I am just not certain about how to make the data locality issue a totally "back-end" concern, so the user doesn't need to worry about it, but still have a performant system for the user too. 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.
