> Le 3 mai 2017 à 19:44, Tim Streater <t...@clothears.org.uk> a écrit : > >> 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? > > Why don’t you write your own wrapper functions for the base SQLite calls. My > set of these functions logs where each call occurs and what the SQL was.
That's indeed an obvious path, and our C++ wrapper can easily do so. It indeed gives us precise context information including the sqlexpanded query when appropriate, but only when SQLite raises an error (which is rather exceptional in released code). Here these are not errors, merely informational messages from SQLite which we can lightly capture on the fly. Logging all detailed context would be unnecessary bulk. Hence the proposal which is, apparently, lighter and only triggers when SQLite has something useful to say. I try to keep things simple and light. :) -- 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
