Malcolm Tredinnick wrote: > Unfortunately, this ticket doesn't solve Ivan's problem of the moment, > as far as I can see.
Yeah, it sends signals in addition to maintaining connection.queries. My point (or one of them) is to replace current hard-coded implementation with something lower-level and less intrusive and then reimplement connection.queries on top of it. And the disable it by default. I'm happy with signals by the way. This is consistent with the way Django reports unhandled exception in core.handlers.base. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
