Changes between Version 1 and Version 9 of Ticket #11287


Ignore:
Timestamp:
Aug 30, 2013, 3:43:48 PM (16 months ago)
Author:
jun66j5
Comment:

Replying to ChrisNelson:

executemany() has different (perhaps buggy) behavior vs. .execute() when no results are found.

No. executemany() is needed instead of inserting multiple rows feature. We have no need to change the select statement.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11287

    • Property Status changed from new to assigned
  • Ticket #11287 – Description

    v1 v9  
    1 As noted in http://trac-hacks.org/ticket/11131#comment:3 and http://www.python.org/dev/peps/pep-0249/#executemany, `.executemany()` is preferred over passing a list of tuples.  This can clean up a number of database accesses, potentially making them more portable and readable.
     1As noted in comment:3:ticket:11131 and http://www.python.org/dev/peps/pep-0249/#executemany, `.executemany()` is preferred over passing a list of tuples.  This can clean up a number of database accesses, potentially making them more portable and readable.