So, should I treat this as a bug? Is this intentionally implemented so that the order in which the items in the traverse query are specified does not reflect the order of the result set? If so, how can I get them in the desired order?
Thanks, Andrei -- --- 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.
