Hi y'all,

    I closed the original ticket because two responses is not enough to 
reopen it. I'm -1 to this change. IMO your issue is really niche and it's 
caused by multiple reasons, i.e. huge table, Meta.ordering by non-indexed 
column, uncaught exception, error reporting layer that calls `repr()` etc. 
and to be honest even with all of this fetching the first 20 rows should 
not crash your production database (I worked with tables that had hundreds 
of millions of records). I'm against this change because it will have a 
negative impact for most of users (like pointed by Luke[1]). It will also 
have a big impact on our documentation ~ 200 examples to change.

Best,
Mariusz

[1] https://code.djangoproject.com/ticket/20393#comment:5

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/c459aec4-23f1-475f-9b9f-0acb2c83b54c%40googlegroups.com.
  • ... Matt
    • ... Ryan Hiebert
      • ... Adam Johnson
    • ... Matt
      • ... Ryan Hiebert
    • ... Matt
    • ... Mariusz Felisiak
      • ... Carlton Gibson
        • ... 'Alexandr Aktsipetrov' via Django developers (Contributions to Django itself)
        • ... James Bennett
          • ... charettes
            • ... Harro
              • ... Mariusz Felisiak
                • ... Matt
                • ... Michel Sabchuk
                • ... Joachim Jablon
                • ... 'Adam Johnson' via Django developers (Contributions to Django itself)

Reply via email to