diff --git a/apsw/__init__.pyi b/apsw/__init__.pyi index 7516cceb..8a87fdd0 100644 --- a/apsw/__init__.pyi +++ b/apsw/__init__.pyi @@ -1877,6 +1877,7 @@ class Connection: .. seealso:: * :ref:`Example ` + * :class:`apsw.ext.Trace` Calls: * `sqlite3_trace_v2 `__ diff --git a/doc/pysqlite.rst b/doc/pysqlite.rst index a575c7a0..8f03d856 100644 --- a/doc/pysqlite.rst +++ b/doc/pysqlite.rst @@ -102,7 +102,14 @@ module: sqlite3's *executescript* method doesn't allow any form of data being returned (it silently ignores any returned data). -* APSW has better :ref:`execution and row tracing `. +* APSW has better :ref:`execution and row tracing `. Both + APSW and sqlite3 wrap `sqlite3_trace_v2 + `__. sqlite3 only lets + you see :meth:`the text of executed statements + `. APSW provides :meth:`a + lot more information `, and allows for + multiple callbacks. And provides a :class:`helpful context block + tracer `. * :doc:`ext` includes: diff --git a/src/apsw.docstrings b/src/apsw.docstrings index 99f311af..815f74e7 100644 --- a/src/apsw.docstrings +++ b/src/apsw.docstrings @@ -2352,6 +2352,7 @@ ".. seealso::\n" \ "\n" \ " * :ref:`Example `\n" \ +" * :class:`apsw.ext.Trace`\n" \ "\n" \ "Calls:\n" \ " * `sqlite3_trace_v2 `__\n" \ diff --git a/src/connection.c b/src/connection.c index 134585b8..7825b5b3 100644 --- a/src/connection.c +++ b/src/connection.c @@ -1477,6 +1477,7 @@ Connection_set_profile(Connection *self, PyObject *const *fast_args, Py_ssize_t .. seealso:: * :ref:`Example ` + * :class:`apsw.ext.Trace` -* sqlite3_trace_v2 sqlite3_stmt_status */