Lodewijk Duymaer van Twist wrote: > I'm tracing queries that my application makes using sqlite3_trace_v2 and > sqlite3_expanded_sql in the callback. The application uses sqlite 3.22.0. > > At some point the software will call sqlite3_exec with the following > statement: > BEGIN TRANSACTION; > DELETE FROM call_lists WHERE id = 11; > END TRANSACTION; > > The output of sqlite3_expanded_sql is: > BEGIN TRANSACTION; > DELETE FROM call_lists WHERE id = 11; > DELETE FROM call_lists WHERE id = 11; > DELETE FROM call_lists WHERE id = 11; > DELETE FROM call_lists WHERE id = 11; > END TRANSACTION; > > Is this normal explaiable behaviour or should I try to provide a repo?
Are you tracing multiple SQLITE_TRACE_xxx events? And <https://www.sqlite.org/c3ref/c_trace.html> says: | An SQLITE_TRACE_STMT callback is invoked when a prepared statement first | begins running and possibly at other times during the execution of the | prepared statement, such as at the start of each trigger subprogram. Regards, Clemens _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
