Hello, +1 from my side. I agree with Simon's proposal and also the email above. It is not really necessary to log *all* of queries also on development servers. If there's something fishy going on nothing would stop me to enable unlimited logging again.
Cheers, Valts. On Mon, Apr 21, 2008 at 3:16 AM, Manuel Saelices <[EMAIL PROTECTED]> wrote: > > Simon is right IMO, but not only for production server... what about > development and preproduction servers? Is usual in projects that you > deploy application in a server for customer or partners, and it's > better to set DEBUG mode for debugging purposes (of course), > tracebacks, URLs debugging, etc. I don't like to restart servers every > day/week to avoid a huge memory consumption. > > Regards, > > On 21 abr, 00:40, "Russell Keith-Magee" <[EMAIL PROTECTED]> > wrote: > > On Mon, Apr 21, 2008 at 6:23 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > > > -1 for the reasons that James Bennett stated above. That it crashes > > > and burns in production is actually a feature in this case. > > > > -1 here too, for exactly the same reason. Add to that the inevitable > > Murphyism that the one time you specify N=10 will be the time that the > > 11th oldest query will be the one causing the problem. > > > > Yours, > > Russ Magee %-) > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
