@Craig: OK. That makes sense, but is there any special significant to a property called "weight" or is it just a convention, where "weight" would still need to be included in the query to have any effect? If so, do you have an example of a query that would go along with your examples? --Eric
On Friday, July 10, 2015 at 11:26:32 AM UTC-5, Craig Trader wrote: > > The meaning of weight for an edge depends upon your application. > > If you're doing a mapping application, weight frequently represents a > value-judgement about that edge versus another combination of edges > (frequently a mix of distance and trip time). Thus if AB is weighted at > 0.5, BC is weighted at 0.5, and AC is weighted at 0.2, it may make more > sense to take the longer path (A->B->C) rather than the direct path (A->C). > > If you're doing a social network application, weight is frequently > equivalent to reliability or strength of relationship. If Alice is a > friend (0.8) of Bob, and Bob is a friend (0.2) of Charlie, then Alice is > likely to have more influence over Bob than Charlie. > > - Craig - > > On Wed, Jul 8, 2015 at 6:10 AM, Riccardo Tasso <[email protected] > <javascript:>> wrote: > >> >> 2015-07-08 5:13 GMT+02:00 Eric24 <[email protected] <javascript:>>: >> >>> Riccardo says his benchmark results show no difference since OrientDB 2.0 >> >> >> That's not my benchmark: Craign said so ( >> https://github.com/wcraigtrader/ogp ). >> >> Riccardo >> >> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- 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.
