[issue8196] sqlit3.paramstyle reported as 'qmark'

Gerhard Häring added the comment: There is too little value changing the paramstyle attribute. I think the documentation clearly states that both parameter binding methods are supported. -- resolution: -> rejected status: open -> closed ___ Python

[issue8196] sqlit3.paramstyle reported as 'qmark'

Gerhard Häring added the comment: I said qmark vs numeric. I. e. vs: execute("UPDATE authors set name = :1, email = :2, comment = :3 WHERE id = :4", (form.name, form.email, form.text, form.id)) The sqlite3 module will always support both paramstyles qmark and named, simply because that is wh

[issue8196] sqlit3.paramstyle reported as 'qmark'

Santiago Gala added the comment: I don't think they are equally clear, at least from the point of view of the code written towards the API. I think that execute("UPDATE authors set name = ?, email = ?, comment = ? WHERE id = ?", (form.name, form.email, form.text, form.id)) is way less clear,

[issue8196] sqlit3.paramstyle reported as 'qmark'

Gerhard Häring added the comment: Thanks for bringing this up. By changing this we would maybe be a little bit closer to PEP 0249. I don't get why the PEP author thinks that 'qmark' is less clear than 'numeric', though. I think they're equally clear. The real reason why I object changing any

[issue8196] sqlit3.paramstyle reported as 'qmark'

Changes by Georg Brandl : -- assignee: -> ghaering nosy: +ghaering ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue8196] sqlit3.paramstyle reported as 'qmark'

New submission from Santiago Gala : >>> import sqlite3 >>> sqlite3.paramstyle 'qmark' The documentation claims that sqlite3 accepts 'named' paramstyle, and :PEP:`249` says in footnote 2: Module implementors should prefer 'numeric', 'named' or 'pyformat' over the other formats b