MySQL for Python / Feature Requests / #21 warning when executemany is performed with separate executes

#21 warning when executemany is performed with separate executes

Milestone: MySQLdb-1.3

Status: open

Owner: Andy Dustman

Labels: MySQLdb (19)

Priority: 5

Updated: 2012-09-19

Created: 2010-11-02

Creator: Mark Dufour

Private: No

please consider adding a warning to executemany, when it is performed using separate execute's, or even removing this feature entirely. imo, executemany should always try to use a single execute or fail loudly, because that is what most users would expect, and it would make for a simpler and more understandable API. of course it's easy enough for users to use a for-loop to do individual executes if executemany doesn't work.. thanks!

Discussion

Most users haven't read http://www.python.org/dev/peps/pep-0249/ then.

    .executemany(operation,seq_of_parameters)

        Prepare a database operation (query or command) and then
        execute it against all parameter sequences or mappings
        found in the sequence seq_of_parameters.

        Modules are free to implement this method using multiple
        calls to the .execute() method or by using array operations
        to have the database process the sequence as a whole in
        one call.

        Use of this method for an operation which produces one or
        more result sets constitutes undefined behavior, and the
        implementation is permitted (but not required) to raise 
        an exception when it detects that a result set has been
        created by an invocation of the operation.

        The same comments as for .execute() also apply accordingly
        to this method.

        Return values are not defined.

warning when executemany is performed with separate executes

MySQL database connector for Python programming

Group

Searches

Help

#21 warning when executemany is performed with separate executes

Discussion