This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author elfring
Recipients elfring
Date 2014-11-27.13:38:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417095519.92.0.197896622793.issue22956@psf.upfronthosting.co.za>
In-reply-to
Content
An interface for parameterised SQL statements (working with placeholders) is provided by the execute() method from the Cursor class at the moment.
https://docs.python.org/3/library/sqlite3.html#sqlite3.Cursor.execute

I assume that the "SQL Statement Object" from the SQLite C interface is reused there already.
http://sqlite.org/c3ref/stmt.html

I imagine that it will be more efficient occasionally to offer also a base class like "prepared_statement" so that the parameter specification does not need to be parsed for every passed command.
I suggest to improve corresponding preparation and compilation possibilities.
History
Date User Action Args
2014-11-27 13:38:39elfringsetrecipients: + elfring
2014-11-27 13:38:39elfringsetmessageid: <1417095519.92.0.197896622793.issue22956@psf.upfronthosting.co.za>
2014-11-27 13:38:39elfringlinkissue22956 messages
2014-11-27 13:38:39elfringcreate