[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Change by Berker Peksag : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.10, Python 3.9 -Python 2.7, Python 3.3, Python 3.4 ___ Python tracker

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Berker Peksag added the comment: New changeset 95e4431804587a0c9d464bb7b3d5f3057bbeaccd by Miss Islington (bot) in branch '3.9': bpo-20364: Improve sqlite3 placeholder docs (GH-25003) https://github.com/python/cpython/commit/95e4431804587a0c9d464bb7b3d5f3057bbeaccd --

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Change by miss-islington : -- nosy: +miss-islington nosy_count: 8.0 -> 9.0 pull_requests: +24135 pull_request: https://github.com/python/cpython/pull/25402 ___ Python tracker

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Berker Peksag added the comment: New changeset 3386ca0b36327afeef8d7eff277b2aed1030c08d by Erlend Egeberg Aasland in branch 'master': bpo-20364: Improve sqlite3 placeholder docs (GH-25003) https://github.com/python/cpython/commit/3386ca0b36327afeef8d7eff277b2aed1030c08d -- nosy:

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Erlend Egeberg Aasland added the comment: Terry, I've created GH-25003 based on your suggested changes. -- ___ Python tracker ___

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Change by Erlend Egeberg Aasland : -- keywords: +patch nosy: +erlendaasland nosy_count: 6.0 -> 7.0 pull_requests: +23761 pull_request: https://github.com/python/cpython/pull/25003 ___ Python tracker

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Michael Wayne Goodman added the comment: Sorry, typo in my last statement. I did *not* verify if the behavior is the same with earlier/later versions. -- ___ Python tracker

[issue20364] Rename & explain sqlite3.Cursor.execute 'parameters' param

Michael Wayne Goodman added the comment: Sorry to resurrect an old bug, but I've also found the docs lacking and I can fill in some gaps with some experimental results. Setup: >>> import sqlite3 >>> conn = sqlite3.connect(':memory:') >>> conn.execute('CREATE TABLE foo (x INTEGER,

[issue20364] Rename explain sqlite3.Cursor.execute 'parameters' param

New submission from Terry J. Reedy: execute(sql[, parameters]) Executes an SQL statement. The SQL statement may be parametrized (i. e. placeholders instead of SQL literals). The sqlite3 module supports two kinds of placeholders: question marks (qmark style) and named placeholders (named

[issue20364] Rename explain sqlite3.Cursor.execute 'parameters' param

R. David Murray added the comment: I wonder if the fact that a sequence is accepted in named mode should actually be considered a bug and not documented. Also, is it really true that the number of items must match even in named mode? I think I remember passing a dict with extra elements,

[issue20364] Rename explain sqlite3.Cursor.execute 'parameters' param

Chris Angelico added the comment: Small quibble: The last sentence capitalizes a Python built-in, which is confusing (Len(seq_dict) must match...). Tweak of grammar to have it not at the beginning of the sentence: Either way, len(seq_dict) must match -- nosy: +Rosuav

[issue20364] Rename explain sqlite3.Cursor.execute 'parameters' param

Terry J. Reedy added the comment: I do not know what the intention was for sequences and named placeholders. Thinking of named tuples made me think it ok. The code might have a hint. Is sqlite3 code maintained here or elsewhere? The current docstring is just 'Executes a SQL statement.', and

[issue20364] Rename explain sqlite3.Cursor.execute 'parameters' param

R. David Murray added the comment: I don't know anything about the current relationship between the external project and the stdlib version. In the (small) changes I've been part of, we have maintained what is in the stdlib without reference to the external project. --