I am getting this error after installation.

It seems to be based on this line:

"ENGINE": "django_query_profiler.django.db.backends.mysql",

When I remove the django_query_profiler, no issue, but when it is in the engine string, it always throws:

  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/django_query_profiler/django/db/backends/mysql/base.py", line 12, in db_row_count
    return cursor.rowcount if not cursor.connection.errno() else -1
AttributeError: 'Connection' object has no attribute 'errno'

Hi Django Query Profiler authors,

I've come across this project while looking for a solution for the current state of limbo at Django-Silk (https://github.com/jazzband/django-silk/issues/465). :)

I've installed the package and configured settings.py and urls.py per https://django-query-profiler.readthedocs.io/en/latest/configuration_instructions.html. However, I hit this error AttributeError: 'Settings' object has no attribute 'DJANGO_QUERY_PROFILER_REDIS_HOST' when running the server.

Could you let me know how I can overcome this problem?

Thank you very much!

Vinh

I seem to be running into a bug but I'm not really sure on why this fails at the point where it fails.

RecursionError at /django_query_profiler/7c1ed3533d2a4c91aa3736812dffe345/QUERY_SIGNATURE maximum recursion depth exceeded while calling a Python object

This is in the file: django_query_profiler/templates/django_query_profiler_level_query_signature.html line 177. If I expand the if statement with {% if query_signature and query_signature.analysis.visible_in_ui %}, this works fine, just does not show the analysis name.

Moz parser can't handle certain Postgresql specific queries and returns a ParseException (e.g. SELECT DISTINCT ON https://www.geekytidbits.com/postgres-distinct-on/).

This results into the QUERY_SIGNATURE view to crash when trying to render the recommendation for those queries.

ParseException at /django_query_profiler/2caa74b2f946492cade911200a7f7d8a/QUERY_SIGNATURE
Expecting one of (binary_and, binary_or, concat, in, neq, offset, and, left join, inner join, group by, not_between, collate nocase, full join, full outer join, order by, between, is, or, left outer join, right join, nlike, nin, right outer join, union, like, limit, having, join) (at char 134), (line:1, col:135)

It relies on moz-sql-parser, which has already been archived and deprecated. https://github.com/mozilla/moz-sql-parser Is there any attempt to make this the successor mo-sql-parsing? https://github.com/klahnakoski/mo-sql-parsing

I looked at the source code for an hour trying to do this, but I wasn't sure. sorry.

The abbreviation "ms" is milliseconds while the abbreviation "μs" is microseconds. There are 1,000 microseconds in a millesecond. The value of the variable it is referencing is also called total_query_execution_time_in_micros. I did a cursory check of the logic behind this variable to verify it is reporting in microseconds:

query_execution_time_in_micros = int((end_time - start_time) * 1000 * 1000)

end_time - start_time is in seconds, multiply by 1,000 is in milleseconds and multiplying again by 1,000 is in microseconds. 👍

While I was in these files, I also fixed some casing of words/acronyms that I saw.

Uses d3 flame-graph, you can click to "zoom" etc.

(Note ported from same feature added to Zenefits internal tool, there's some small handling here for "multiple roots" which maybe can't happen with the open-source version (i.e. middleware vs view for the same request UUID.)

• Adding Django 3.1 and 3.2 in classifiers
• Adding Python 3.9 in classifiers
• Adding Django 3.2 in tox for testing on CI
• Removing Django tip for now ; Going to add it back later in a separate PR

I'm getting the following error when using the Chrome extension.

The error seems to be coming from here: https://github.com/django-query-profiler/django-query-profiler/blob/04483ccc7dd3ef93f51c35f938e77347b050bd21/django_query_profiler/client/middleware.py#L57

There is a comment that says:

The exception can happen because of two reasons:

1. redis throws exception
2. detailed_view_url not setup in urls.py

I am not using Redis and I have triple-checked that I have added path('django_query_profiler/', include('django_query_profiler.client.urls')) to my urls.py. However, the comment does reference detailed_view_url and I am unsure what that is referring to. I went over the setup instructions multiple times to confirm I have configured my app correctly. I am using the SQLite version of the database engine. I have also messed with the order of the middleware too since I know that can be problematic sometimes.

I am using Python 3.8, Django 3.1.5, DRF 3.12.1.

• Was getting some package incompatibility error for mo-future
• We are not using the package directly
• Maybe it means we should have a requirements.txt file ?
• Figured out the version used by running pip freeze
• Added fix for djangotip
• Fixed for flake8

1. In the detailed view, we should show recommendation for decreasing queries only when it is one of select_related or prefetch_related
2. Adding a constructor param to enum for visible_in_ui to see if we should show the recommendation in chrome plugin

Hi, this currently fails to install on Python 3.10, but only because there is no 3.10 compatible wheel available for the mmh3 dependency.

Is it essential that mmh3 be used as the hash function here? Something more standard like the standard library's hashlib might prevent this issue from occurring in the future.