[issue12993] prepared statements in sqlite3 module

Changes by Georg Brandl : -- resolution: -> works for me status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue12993] prepared statements in sqlite3 module

poq added the comment: This can be closed. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12993] prepared statements in sqlite3 module

Mayur & Angela Patel-Lam added the comment: Okay, I missed that in the documentation. I was looking for a handle to a prepared statement. I suppose it's hashing on the text of the SQL statement to determine equivalence? I'm willing to retract the request. I need to restructure my code a litt

[issue12993] prepared statements in sqlite3 module

poq added the comment: The sqlite3 module already uses prepared statements. Quoting from the documentation: "The sqlite3 module internally uses a statement cache to avoid SQL parsing overhead. If you want to explicitly set the number of statements that are cached for the connection, you can

[issue12993] prepared statements in sqlite3 module

Changes by Ned Deily : -- nosy: +ghaering ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue12993] prepared statements in sqlite3 module

New submission from Mayur & Angela Patel-Lam : The sqlite3 module is wonderful, but the one advantage that C/C++ coders have using that system is the ability to use precompiled/prepared SQL statements. Some SQL databases like Postgresql allow you to precompile statements using special SQL sta