milliseconds or less of difference
because the setrange only has 2 options for the where clause in the sql versus the setfilter which has more.
So the time it takes to parce the string in the setfilter - the time it takes to define which of the 2 options it is for the setrange is the difference. There is no difference in the SQL statement sent to the db
|Pressing F1 is so much faster than opening your browser| |To-Increase|
Comments
SETFILTER if you want to filter by any STRING.
Andwian
i think setfilter should be fast rather than setrange.
i was talking about, after setcurrentkey if you are using setrange or setfilter then which will be fast?
because the setrange only has 2 options for the where clause in the sql versus the setfilter which has more.
So the time it takes to parce the string in the setfilter - the time it takes to define which of the 2 options it is for the setrange is the difference. There is no difference in the SQL statement sent to the db
|To-Increase|
But it is good practice to always use SETRANGE if you can and SETFILTER ONLY if you have no other option.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!