On 1/11/15, Venkat Murty <vmu...@fiberlink.com> wrote: > > >>> I am expecting two usable entries in sqlite3_index_info with >>> aConstraint[i].iColumn = 0 and aConstraint[i].op == >>> SQLITE_INDEX_CONSTRAINT_EQ for each check >> >> What actually happens is that SQLite transforms the query into >> >> SELECT stamp, to_text(value) FROM store WHERE id IN (42,24). >> >> The xBestIndex method does not distinguish between == and IN, so only >> a single == constraint will be mentioned in the xBestIndex call. >> > > How to i extract multiple values in xFilter -- int argc, sqlite3_value > **argv ? If i specify aConstraintUsage[].argvIndex = 1 then i should expect > a list of values (42 and 24) in argv[0]. >
xFilter will be called multiple times, once for each value in the RHS of the IN operator. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
