Question

We’ve got some really strange extraneous DB hits happening in our project. Is there any way to monitor where the requests are coming from, possibly by line number? The SQL printing middleware helps, but we’ve looked everywhere those kinds of requests might be generated and can’t find the source.

If the above isn’t possible, any pointers on narrowing down the source would be greatly appreciated.

Answer 1

To find the code executing queries, you can install django-debug-toolbar to figure out what commands are being executed and which tables they’re operating on.

Once you’ve done that, try hooking into the appropriate Django signals for those models and using print and assert to narrow the code.

I’m sure there’s a better way to do some of this (a python debugger?) but this is the first thing that comes to mind and probably what I would end up doing myself.