On Tue, Mar 28, 2017 at 12:51 PM, Dominique Devienne <ddevie...@gmail.com> wrote:
> On Tue, Mar 28, 2017 at 11:00 AM, Hick Gunter <h...@scigames.at> wrote: > > > > > The "estimated cost" is described as "how many disk IO operations are > > expected". Version higher than 3.8.2 allow setting an "estimatedRows" > > (default: 25) and versions above 3.9.0 allow setting a flag that > indicates > > that 0 or 1 rows will be returned (i.e. the constraints form a "unique > > index"). > > > > Thanks for the RTFM. That helps. Looks like I have about 3 years worth of > catch-up to do on sqlite3_index_info. > > Thanks, Dominique, Hick I looked at the additional fields of sqlite3_index_info and probably they're of no use for me, at least they don't provide some enforcing of my particular index. As for my problem queries, they usually involve "order by" or "group by", that's when the planner (despite the obvious bias from me about the particular index) decides to provide only one of my two required fields. Also interesting that actually what I called input/output approach, sqlite implemented calling it table-valued functions (probably starting 3.9.0) ( https://sqlite.org/vtab.html#tabfunc2). To make my tables compatible with this syntax, I just had to append HIDDEN to the "input" fileds of the table definition. But seems like changing to this definition doesn't affect the planner. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
