sqlite> explain query plan SELECT id FROM tour LIMIT 1;
0|0|0|SCAN TABLE tour USING COVERING INDEX tour_unsorted_path_idx
(~1000000 rows)
I am not still sure I understand completely the output of explain
query plan. But for sure, a small number in the end sounds a good
thing. In my application after working with indexes and removing
the big numbers of rows I got a great speed up.
I just have a question about query written in the begin, in my
application I use it to know if a table is empty. I execute it
and just use sqlite3_step return value. Errors a part, if it is
SQLITE_DONE the table is empty, if it is SQLITE_ROW it is not.
To get this simple result, sqlite3 actually scans the whole
table? If it is so, can be avoided?
Thanks,
Paolo
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
