Logically, I don't see a reason why the query is *obliged* to behave the way it did before, but I will forward the bug report to Igor to confirm the current behavior is legitimate.
Logically, I don't see a reason why the query is *obliged* to behave the way it did before, but I will forward the bug report to Igor to confirm the current behavior is legitimate.