On Sat, Apr 19, 2008 at 2:37 AM, Simon Willison <[EMAIL PROTECTED]> wrote: > I've noticed that a LOT of people get bitten by the problem where > every SQL statement is logged if DEBUG=True, resulting in huge memory > consumption after a while. This problem seems particularly common for > import scripts, which are often run in development (hence with DEBUG > on) and can involve thousands of queries.
The flip side of the argument, though, is that it means someone who leaves DEBUG=True on a live deployment will very quickly have a noticeable problem, and that's a useful behavior. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
