+1 - useful for user code that guards against accidental poor ORM usage. On Monday, 18 August 2014 05:47:15 UTC+10, jdunck wrote: > > I use this method on my own test subclasses, and I find it useful as a > tripwire: a cause for review and consideration, more than a hard error. Did > the number of queries go up on this change? Is that reasonable or a > mistake? Have we blown the perf budget so we should refactor? Or maybe the > number should just be raised to something that seems like a reasonable next > tripwire. > > These limits aren't flaky or false positives, so they seem useful supports > given a reasonable test suite otherwise. > >> >>
-- 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/33a1da8e-6ae5-4e14-a829-dc679e95c169%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
