Scott, Is it really a full table scan or just an index scan (at least in the case where no data is needed from the table as in the original sample that had no join or where clause).
Thanks, Sam On Thu, Apr 3, 2008 at 4:12 PM, Scott Hess <[EMAIL PROTECTED]> wrote: > A little bit more info: SELECT COUNT(*) is implemented as a full > table scan, so SQLite is visiting every row in the table, which will > get slower and slower as the table gets bigger and the database > fragments. This differs from many database engines (which implement > an optimization for this) Doing the trigger thing means that it only > visits the specific row that contains the count. > > -scott > > -- ----------------------------------------------------------------- We're Hiring! Seeking passionate Flex, C#, or C++ (RTSP, H264) developer. Position is in the Washington D.C. metro area. Contact [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
