From f9b3706df65c4962646587b437a4eb39289dfd4c Mon Sep 17 00:00:00 2001 From: Erlend Egeberg Aasland Date: Fri, 22 Jul 2022 09:34:39 +0200 Subject: gh-81040: Improve sqlite3.Cursor.rowcount docs (#94940) --- Doc/library/sqlite3.rst | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst index a7581f2..583a36d 100644 --- a/Doc/library/sqlite3.rst +++ b/Doc/library/sqlite3.rst @@ -966,18 +966,11 @@ Cursor Objects .. attribute:: rowcount - Although the :class:`Cursor` class of the :mod:`sqlite3` module implements this - attribute, the database engine's own support for the determination of "rows - affected"/"rows selected" is quirky. - - For :meth:`executemany` statements, the number of modifications are summed up - into :attr:`rowcount`. - - As required by the Python DB API Spec, the :attr:`rowcount` attribute "is -1 in - case no ``executeXX()`` has been performed on the cursor or the rowcount of the - last operation is not determinable by the interface". This includes ``SELECT`` - statements because we cannot determine the number of rows a query produced - until all rows were fetched. + Read-only attribute that provides the number of modified rows for + ``INSERT``, ``UPDATE``, ``DELETE``, and ``REPLACE`` statements; + is ``-1`` for other statements, + including :abbr:`CTE (Common Table Expression)` queries. + It is only updated by the :meth:`execute` and :meth:`executemany` methods. .. attribute:: lastrowid -- cgit v0.12