Yes a non partial index beyond column 64 works as I would expect. - Deon
> On Oct 18, 2018, at 12:34 PM, Shawn Wagner <shawnw.mob...@gmail.com> wrote: > > Does a normal non-partial index make a difference in the query plan? > >> On Thu, Oct 18, 2018, 12:30 PM Deon Brewis <d...@mylio.com> wrote: >> >> Hi, >> >> I seem to have run into a limit where SQLITE doesn't use an index >> correctly if an indexed column is over the 64th column in the table. It's a >> partial index like: >> >> CREATE INDEX idx ON >> table(A, B DESC, C, D) >> WHERE A > 0 >> >> Where A and B are columns 70 and 72 on 'table'. >> >> I know about the 64-column limitation for covering indexes: >> >> http://sqlite.1065341.n5.nabble.com/Max-of-63-columns-for-a-covering-index-to-work-td68945.html >> >> However, this isn't a covering index, it's a partial index. But it seems >> to run into the same limit. Even if I forced in the index into a query it >> still does a "USE TEMP B-TREE" at the end to satisfy a simple "ORDER BY A, >> B DESC" query. After I re-ordered the table, it magically started working. >> >> Is there any better documentation anywhere (other than the archive) of all >> of the cases to which the 64-column limit applies? >> >> - Deon >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
