Sébastien Corbin
Sébastien Corbin
After few days of real-world testing, the `ready()` method is not development-proof with the `runserver` command. I'll update this PR to switch to classic context manager on the middleware.
Another option: rely on `connection_created` signal
Could you give us more information about where your query is placed in your code? In middleware, in a view? Also if you can give us a stacktrace of both...
OK so it seems the EXPLAIN re-execute the query, I'll need to check that, can you give me the database django engine you are using?
I think this is out of our hands then, from https://www.postgresql.org/docs/current/sql-explain.html > The ANALYZE option causes the statement to be actually executed, not only planned. Then actual run time statistics...
Right, I'll keep that opened then :)
If you look at the HTML/CSS/JS of the django-silk views, a lot can be streamlined to basic HTML/CSS instead of the overly complex (and exploded) current JS code. If you...
Please provide the error and your tenant-schema (DB) config
It could be that you included the middleware twice, but this should be check in the ready of `SilkAppConfig`.
Also found another consequence using `virtualenvwrapper`, which is a collection of bash functions defining shortcuts for python virtualenvs. The error was `/usr/local/bin/virtualenvwrapper.sh:442: parse error near '>&'` which was referring to...