I'd say it is because the rids are physical locations, so it is easy for ODB to just go directly to the records and get them with the FROM clause. Whereas, the WHERE clause is a filter, which means there needs to be a separation of the records from a complete list (scan) of all the records. One would think the system would be smart enough to reduce the WHERE/IN when using @rid to the simple SELECT/FROM form, but I am sure there are technical reasons why this isn't directly possible.
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.
