On 4 May 2017 at 01:16, Olivier Mascia <o...@integral.be> wrote: > > Le 3 mai 2017 à 18:46, Richard Hipp <d...@sqlite.org> a écrit : > > > > On 5/3/17, Olivier Mascia <o...@integral.be> wrote: > >> automatic index on sqlite_sq_25FA4563E0(ID) (284) > >> ... > >> > >> I guess they mean SQLite decided to build some temporary index for some > >> query execution, just as for the first case. But here the table itself > looks > >> like internal and temporary. What can I interpret from these? > > > > Yes. Those sqlite3_sq_... tables are going to be materializations of > > views and/or subqueries. The "sq" stands for "subquery". > > Thanks Richard. > What recommended path, if there's one favored, should I take to make it > easy to identify which queries induce those indexes on subqueries? >
A [conditional] breakpoint in your logging callback might suffice, if you can reproduce in debug? In general it might be nice to have some context available from the logging function; eg. at present it's not even possible to determine which connection was responsible for the warning. -Rowan _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
