Message144341
| Author |
Mayur.&.Angela.Patel-Lam |
| Recipients |
Mayur.&.Angela.Patel-Lam, ghaering, poq |
| Date |
2011年09月20日.16:40:27 |
| SpamBayes Score |
8.5493475e-06 |
| Marked as misclassified |
No |
| Message-id |
<CAHwaBAVTHS7A36cqERZa5Oa_8_pcn7RKH_1EDPSc9GRinxBrMQ@mail.gmail.com> |
| In-reply-to |
<1316296046.48.0.323470592892.issue12993@psf.upfronthosting.co.za> |
| Content |
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 little
bit to take advantage of this feature.
On Sat, Sep 17, 2011 at 5:47 PM, poq <report@bugs.python.org> wrote:
>
> poq <poq@gmx.com> 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 set the cached_statements parameter. The
> currently implemented default is to cache 100 statements."
>
> ----------
> nosy: +poq
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue12993>
> _______________________________________
> |
| Files |
| File name |
Uploaded |
|
unnamed
|
Mayur.&.Angela.Patel-Lam,
2011年09月20日.16:40:26
|
|