[issue18691] sqlite3.Cursor.execute expects sequence as second argument.

Berker Peksag added the comment: I think the name "parameters" causes a confusion here. It basically means def execute(sql, parameters): not def execute(sql, *parameters): So ``con.execute('insert into foo values (?, ?)', (4, 5))`` is the correct usage of the API. Also, this looks

[issue18691] sqlite3.Cursor.execute expects sequence as second argument.

Mark Lawrence added the comment: @Andrew your words describe the Cursor execute method but your examples show the Connection execute method, can you clarify please. -- nosy: +BreamoreBoy, ghaering ___ Python tracker

[issue18691] sqlite3.Cursor.execute expects sequence as second argument.

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue18691] sqlite3.Cursor.execute expects sequence as second argument.

New submission from Andrew Myers: Sorry if this isn't the place for this, it is my first python bug report. In PEP 249 Python database API specifiction 2.0 the Cursor execute method[1] is described as taking a variable number of arguments for substitution of '?' in the SQL string. In the docu