Some examples of these would be great, Dr. Hipp. Thanks. On 2017-03-31 09:06, Richard Hipp wrote:
> On 3/31/17, aotto <aotto1...@t-online.de> wrote: > >> I already have a working implementation with [a] close [to] empty >> *xBestIndex and *xFilter. >> >> 6) I expect for a primitive WHERE clause like "rep=XXX" some kind of access >> optimization... > > Your xBestIndex and xFilter functions must implement the desired optimization. > > The xBestIndex and xFilter routines work as a team. xBestIndex is > passed information about the WHERE clause. xBestIndex uses that > information to realize that "rep=XXX" is present, sets fields of > sqlite3_index_info that cause the XXX value to be passed into xFilter, > then sets idxNum or idxStr to tell xFilter what algorithm to use. > xFilter will use the idxNum or idxStr values to recognize that it > should jump immediately to rep=XXX. > > I'll see if I can work up some examples of this later today... _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
