-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 0.96.2
-
Component/s: None
-
None
There is no good messaging right now when a query is made with both a top-level query
{foo:bar}and a mixed in {$orderby:...}. We can create a synthetic cursor failure in this case and give a good warning message.