> 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". > > -- > D. Richard Hipp
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? Would there be a cheap way for SQLite to log some more user-realm context about these? Maybe simply emitting a second call to the log function right after these messages code 284 where the third parameter (msg) would simply point at the prepared statement SQL text (just as sqlite3_sql(sqlite3_stmt*) returns? -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia, http://integral.software _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users