> On 17 oct. 2015, at 10:19, Claude Paroz <cla...@2xlibre.net> wrote: > > I like the idea. However, instead of monkey-patching the Django > CursorDebugWrapper like DDT is doing now, I'd rather see a solution where we > use dynamic logging configuration to output the SQL commands, if possible.
Since the option would also be available for runserver, it would fill a gap whenever the DDT isn’t usable e.g. when using Django as an API in a SPA. On a related note, it would also be interesting to rework the DDT to hook to the django.db.backends logger instead of monkey-patching. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/D1444DF0-EE3B-44EF-A9F1-A6C848C24577%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
