Link Trace to trace stuff

rogerbinns · Nov 17, 2024 · f3223ee · f3223ee
1 parent 7a3ccb9
commit f3223ee
Show file tree

Hide file tree

Showing 4 changed files with 11 additions and 1 deletion.
diff --git a/apsw/__init__.pyi b/apsw/__init__.pyi
@@ -1877,6 +1877,7 @@ class Connection:
         .. seealso::
 
           * :ref:`Example <example_trace_v2>`
+          * :class:`apsw.ext.Trace`
 
         Calls:
           * `sqlite3_trace_v2 <https://sqlite.org/c3ref/trace_v2.html>`__

diff --git 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 <tracing>`.
+* APSW has better :ref:`execution and row tracing <tracing>`.  Both
+  APSW and sqlite3  wrap `sqlite3_trace_v2
+  <https://www.sqlite.org/c3ref/trace_v2.html>`__.  sqlite3 only lets
+  you see :meth:`the text of executed statements
+  <sqlite3.Connection.set_trace_callback>`.  APSW provides :meth:`a
+  lot more information <apsw.Connection.trace_v2>`, and allows for
+  multiple callbacks.  And provides a :class:`helpful context block
+  tracer <apsw.ext.Trace>`.
 
 * :doc:`ext` includes:
 

diff --git a/src/apsw.docstrings b/src/apsw.docstrings
@@ -2352,6 +2352,7 @@
 ".. seealso::\n" \
 "\n" \
 "  * :ref:`Example <example_trace_v2>`\n" \
+"  * :class:`apsw.ext.Trace`\n" \
 "\n" \
 "Calls:\n" \
 "  * `sqlite3_trace_v2 <https://sqlite.org/c3ref/trace_v2.html>`__\n" \

diff --git 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 <example_trace_v2>`
+    * :class:`apsw.ext.Trace`
 
   -* sqlite3_trace_v2 sqlite3_stmt_status
 */