This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erlendaasland
Recipients erlendaasland
Date 2020-04-18.11:56:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1587210970.59.0.35117859461.issue40318@roundup.psfhosted.org>
In-reply-to
Content
Currently, we're using the sqlite3_trace() for tracing statements. This API was been superseded by sqlite3_trace_v2() in SQLite3 v3.14 back in August 2016. Proposing to migrate to the new API, which allows more fine grained control over what to trace, and also opens up the door to stuff like prepared statement status variables.

See https://sqlite.org/c3ref/trace_v2.html, https://sqlite.org/c3ref/c_trace.html, https://sqlite.org/c3ref/c_stmtstatus_counter.html, and https://sqlite.org/c3ref/experimental.html.

Attached patch (against master) uses the new API if available. Make test completes without failures.
History
Date User Action Args
2020-04-18 11:56:10erlendaaslandsetrecipients: + erlendaasland
2020-04-18 11:56:10erlendaaslandsetmessageid: <1587210970.59.0.35117859461.issue40318@roundup.psfhosted.org>
2020-04-18 11:56:10erlendaaslandlinkissue40318 messages
2020-04-18 11:56:10erlendaaslandcreate