Perhaps we ought to just keep the current behavior when DEBUG is True (it seems so obvious now, I can't believe it wasn't the first thing I suggested)? Django does lots of helpful things in DEBUG mode at the expense of performance. I think this would be an innocuous change for most people.
It is not the most important thing to remove behavior that most of users > use because we want to fix an edge case that was reported twice in the last > six years. > I don't consider any of those *individual *conditions to trigger the problem "off the beaten path" for a bigger production Django site. All of them *combined *is obviously extremely rare, but it will effect someone else eventually*. *It doesn't sit well with me to not fix the issue. Django should be reliable in production for any combination of those conditions. On Wednesday, October 16, 2019 at 12:14:37 AM UTC-7, Mariusz Felisiak wrote: > > W dniu środa, 16 października 2019 07:53:05 UTC+2 użytkownik Harro napisał: >> >> Yes, it's a complicated issue, but isn't the SQL query the ultimate >> representation of which methods are called or not? >> >> Having the query evaluated during debugging has been shown to be harmful >> in certain situations, isn't that the most important thing to fix? >> > > Current behavior is extremely valuable IMO. It is not the most important > thing to remove behavior that most of users use because we want to fix an > edge case that was reported twice in the last six years. I agree that we > can clarify this in docs. SQL query is not a solutions because not all of > ORM users know SQL. Moreover the current `repr()` shows values from DB that > we'll miss showing only SQL. You can check in the Django documentation how > users use the current `repr()` e.g. in tutorials. > > Best, > Mariusz > -- 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/689bd01d-a949-4e65-9cac-357fefa56680%40googlegroups.com.
