Fixed a false alarm in the ordering safeguard

The check verifying how indexed content is ordered looked at the whole database query instead of just the ordering instruction, so an unrelated mention of reverse order elsewhere in the query would have wrongly reported a problem. It now examines only the instruction it is judging.