3 ms·
Very true, that's what I was thinking, and saw this post http://stackoverflow.com/questions/15856604/django-mysql-prepared-statements http://stackoverflow.com/
by hardwaresofton 13y ago
Very true, that's what I was thinking, and saw this post
http://stackoverflow.com/questions/15856604/django-mysql-prepared-statements http://stackoverflow.com/questions/15856604/django-mysql-pre...
and read "django has no concept of connection pooling, and every page view uses a brand new database connection. MySQL prepared statements only exist for the life of the connection/session in which they are defined" on that page... So they're somewhat connected right? My understanding of a prepared statement was a statement that a *SQL server caches for quick use -- which is only kind of right (looked it up again @ https://en.wikipedia.org/wiki/Prepared_statement https://en.wikipedia.org/wiki/Prepared_statement and it's not too far off).
Then question marks went off as to why this still wasn't a thing yet.
- est 13y agoYou are correct. Prepared statements without connection pooling is moot