[issue41829] sqlite3.Row always read as tuple when supplied to executemany

[Tony Wu]

Change by Tony Wu :


--
nosy: +ghaering

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41829] sqlite3.Row always read as tuple when supplied to executemany

[Tony Wu]

New submission from Tony Wu :

Supplying a sequence or sqlite3.Row objects to sqlite3.Connection.executemany 
will cause the Row objects to be interpreted as Sequences instead of Mappings 
even if the statement to be executed uses named parameter substitution.

That is, values in the Rows are accessed using their numerical indices instead 
of column names.

This script demonstrate how this is unexpected behavior.

Issue found in Python 3.8.5 and 3.7.6.

--
components: Extension Modules
files: row_substitution.py
messages: 377295
nosy: tony.wu
priority: normal
severity: normal
status: open
title: sqlite3.Row always read as tuple when supplied to executemany
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file49471/row_substitution.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com