Richard Hipp schrieb am 17.05.2013 17:06:
Furthermore, the "id" is unique so if there is a constraint on the "id" the query planner will always use that constraint to look up the rows in the table directly, rather than going through an index, since doing so will be about twice as fast as using an index.
It's not necessarily faster. If using the INTEGER PRIMARY KEY index means to scan through thousands of rows then an index lookup of only a handful of rows would be faster. That's why I'd like the implicit index to be ANALYZEd and weighted as well (at least with SQLITE_ENABLE_STAT3).
regards Gerd _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
