There is no good messaging right now when a query is made with both a top-level query

and a mixed in {$orderby:...}. We can create a synthetic cursor failure in this case and give a good warning message.