Clarify the meaning of "number of affected rows" in the DB-API 2.0
as discussed on the db-sig list.
This commit is contained in:
parent
8d1c599b2f
commit
32046dbe54
20
pep-0249.txt
20
pep-0249.txt
|
@ -1,7 +1,7 @@
|
||||||
PEP: 249
|
PEP: 249
|
||||||
Title: Python Database API Specification v2.0
|
Title: Python Database API Specification v2.0
|
||||||
Version: $Revision$
|
Version: $Revision: 56119 $
|
||||||
Last-Modified: $Date$
|
Last-Modified: $Date: 2007-06-28 22:11:32 +0200 (Thu, 28 Jun 2007) $
|
||||||
Author: mal@lemburg.com (Marc-André Lemburg)
|
Author: mal@lemburg.com (Marc-André Lemburg)
|
||||||
Discussions-To: db-sig@python.org
|
Discussions-To: db-sig@python.org
|
||||||
Status: Final
|
Status: Final
|
||||||
|
@ -287,7 +287,7 @@ Cursor Objects
|
||||||
This read-only attribute specifies the number of rows that
|
This read-only attribute specifies the number of rows that
|
||||||
the last .execute*() produced (for DQL statements like
|
the last .execute*() produced (for DQL statements like
|
||||||
'select') or affected (for DML statements like 'update' or
|
'select') or affected (for DML statements like 'update' or
|
||||||
'insert'). [9]
|
'insert').
|
||||||
|
|
||||||
The attribute is -1 in case no .execute*() has been
|
The attribute is -1 in case no .execute*() has been
|
||||||
performed on the cursor or the rowcount of the last
|
performed on the cursor or the rowcount of the last
|
||||||
|
@ -1127,20 +1127,6 @@ Footnotes
|
||||||
implement the tp_iter slot on the cursor object instead of the
|
implement the tp_iter slot on the cursor object instead of the
|
||||||
.__iter__() method.
|
.__iter__() method.
|
||||||
|
|
||||||
[9] The term "number of affected rows" generally refers to the
|
|
||||||
number of rows deleted, updated or inserted by the last
|
|
||||||
statement run on the database cursor. Most databases will
|
|
||||||
return the total number of rows that were found by the
|
|
||||||
corresponding WHERE clause of the statement. Some databases
|
|
||||||
use a different interpretation for UPDATEs and only return the
|
|
||||||
number of rows that were changed by the UPDATE, even though
|
|
||||||
the WHERE clause of the statement may have found more matching
|
|
||||||
rows. Database module authors should try to implement the more
|
|
||||||
common interpretation of returning the total number of rows
|
|
||||||
found by the WHERE clause, or clearly document a different
|
|
||||||
interpretation of the rowcount attribute.
|
|
||||||
|
|
||||||
|
|
||||||
Acknowledgements
|
Acknowledgements
|
||||||
|
|
||||||
Many thanks go to Andrew Kuchling who converted the Python
|
Many thanks go to Andrew Kuchling who converted the Python
|
||||||
|
|
Loading…
Reference in New Issue