On 15 nov. 2013, at 18:38, [email protected] wrote: > Every time I get a failure on one of these types of tests I go in and edit > the code to print out the queries that were executed. There's no way to > troubleshoot the problem without know the queries.
I have also typed `from django.db import connection; print(connection.queries)` countless times. We can debate whether assertNumQueries is a good practice — and with what I know of Django’s source code, I don’t doubt it’s an issue for third-party backends. Regardless I support making the failure message more useful. — Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/13B03AD3-3333-47C7-8040-3860A4067FFC%40polytechnique.org. For more options, visit https://groups.google.com/groups/opt_out.
