Basically, the DB size and compactness state influences the speed at
which values are read. (Every update implies a read).
Add to that the fact that these functions verge on the bottom edge of
time consumers... It's like testing diffusion speed of a perfume in a
hurricane.
Glad you found the close competition between most-optimal solutions.
On 2017/02/15 8:43 PM, Cecil Westerhof wrote:
2017-02-15 14:18 GMT+01:00 Cecil Westerhof <cldwester...@gmail.com>:
The OR version is the least efficient and it look likes the BETWEEN
version 2 is the most efficient. It looks like it uses less user and more
sys.
Which is the most efficient is also dependent on the state of the database
itself. I compacted the database and now sometimes NOT BETWEEN is more
efficient and sometimes NOT BETWEEN version 2 is more efficient.
The OR version is always the least efficient.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
