Often when using mysqldb on really large databases
there is a potential to issue huge queries which would
just take way too long. This is obviously not ideal,
but the risk is that having a very slow query on the
server may cause unacceptable performance problems.
It would be nice to add the safety check in the cursor
class to ensure that the query doesnt take too long -
if it does it should be killed.
For example see:
Where a threading.Timer is used to time the query
killing it if it takes too long.
This is essential for shared sites where any query
longer than a few seconds can really affect performace.
Log in to post a comment.