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
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.
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 tha
-1 for the reasons that James Bennett stated above. That it crashes
and burns in production is actually a feature in this case.
- Eric Florenzano
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" g
> Same goes for ignoring pyc files everywhere.
You can tell Subversion to add global ignores on your side of it.
See ~/.subversion/config. As for Windows, I don't know.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
I'm +1 on this.
Although, there was a mistake in one of the replies.
Simon's intended behaviour is:
DEBUG_SQL_LOG_LIMIT = 200 (logs last 200 queries)
DEBUG_SQL_LOG_LIMIT = None (logs all queries)
DEBUG_SQL_LOG_LIMIT = 0 (logs nothing)
Rob
On Apr 19, 8:37 am, Simon Willison <[EMAIL PROTECTED]
+1 also, but I'll suggest keeping the ability to get aggregate
statistics, e.g.,
django.db.connection.total_queries
django.db.connection.total_query_time
(and maybe the whole queries list should be renamed as
django.db.connection.recent_queries, so as not to suggest that it's
actually all of them
> What do people think of having the debug SQL log limited to only
> storing the last N queries, with N set to something sensible like 200
> by default? This behavior could be controlled by a setting so if
> people want to log everything they can:
>
> DEBUG_SQL_LOG_LIMIT = 200 # Set to 0 to disabl
Kenneth Gonsalves wrote:
> On 20-Apr-08, at 12:47 AM, Steve Holden wrote:
>
>>> I wouldn't even call the current svn head a beta-quality product
>>>
>>>
>> Which is probably why it isn't yet a beta release?
>>
>
> what I meant is that it is stable and production ready and that it is
