Gerhard Häring <g...@ghaering.de> 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 what the underlying SQLite engine supports. What paramstyle
says is mostly important for third-party software that works across multiple
DB-API compliant database modules. paramstyle enables them to use database
supported parameter binding.
In reality, though, there will hardly be a wrapper for DB-API modules that does
*not* need to special-case anything depending on the underlying database. So
they will hardly ever rely only on the paramstyle and threadsafety parameters.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8196>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
