From: Georg Brandl Date: Thu, 23 Aug 2007 20:40:01 +0000 (+0000) Subject: Bug #1573854: fix docs for sqlite3 cursor rowcount attr. X-Git-Tag: v2.6a1~1455 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=891f1d339b742986d0abdc288d02cfdf57121e4e;p=python Bug #1573854: fix docs for sqlite3 cursor rowcount attr. --- diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst index 707092b027..bee32e67bf 100644 --- a/Doc/library/sqlite3.rst +++ b/Doc/library/sqlite3.rst @@ -440,9 +440,6 @@ A :class:`Cursor` instance has the following attributes and methods: attribute, the database engine's own support for the determination of "rows affected"/"rows selected" is quirky. - For ``SELECT`` statements, :attr:`rowcount` is always None because we cannot - determine the number of rows a query produced until all rows were fetched. - For ``DELETE`` statements, SQLite reports :attr:`rowcount` as 0 if you make a ``DELETE FROM table`` without any condition. @@ -453,6 +450,9 @@ A :class:`Cursor` instance has the following attributes and methods: 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. + .. _sqlite3-types: