New submission from Erlend Egeberg Aasland <erlend.aasl...@innova.no>:
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. ---------- components: Library (Lib) files: 0002-Use-new-sqlite3_trace_v2-API-if-possible.patch keywords: patch messages: 366702 nosy: erlendaasland priority: normal severity: normal status: open title: Migrate to SQLite3 trace v2 API versions: Python 3.8, Python 3.9 Added file: https://bugs.python.org/file49073/0002-Use-new-sqlite3_trace_v2-API-if-possible.patch _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40318> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
