-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Django Toolbar SQL queries are shown as none #1124
Comments
(in my case, I'm using Django 1.11.18 |
We noticed that upgrading from Django 2.1.4 -> 2.1.5 fixed it for us. OS: Mac |
I had same issue with django debug toolbar. Seems like mysqlclient was the problem. I downgraded mysqlclient from version 1.3.14 to 1.3.13 and it's working now. |
I played with various mysql client versions and was still seeing none. I'm also getting 'none' as the output from runserver_plus (from django extensions) with the optional --print-sql. Just more data points, but it does suggest this is an issue outside DDT. Fwiw, I can get the queries when debugging with PyCharm. So, I can combine the timing data from DDT and get the query from PyCharm. |
@kiruh your recommendation to downgrade mysqlclient worked for me OS: arch linux Django==2.0.5 |
FWIW, I just ran into the same issue. Django 1.11.6 Choosing a different mysqlclient version fixed it for me. I tried downgrading to 1.3.12 and upgrading to 1.4.4, both worked for me. I had this problem when I tried logging the queries using |
The latest version of Django 2.1 solves this problem. This is still a problem for Django 1.11. As per this thread, Django 1.11 won't fix this. Closing this issue. |
I have the same problem, in my case with python 3.6 and django 1.11, downgrade mysqlclient fix it Django==1.11.29 |
Sql queries are not shown the queries timer is shown where as the queries are shown as none.
Below is the version used.
OS:Windows10
Django | | 2.1.4
Python | | 3.7.1
debug_toolbar | Debug Toolbar | 1.11
rest_framework | Django REST framework | 3.9.0
The text was updated successfully, but these errors were encountered: