>Not necessarily. SCAN is Rushmore optimizable with a FOR clause if you have an index on what you are scanning for. So just because you have removed the order on the table, rushmore should still use the index to scan.
>
>>So, would you suggest me to switch? I believe I solved the problem by removing order, but I'm not certain...

Right. But please re-read the original message. My problem is that SCAN didn't work, when I have order set and was changing part of the index expression. Moreover, in some cases it worked fine, but in some it didn't. Removing order seems to fix the problem. But how can I be 100% sure, that it's now correct? :)