Sometimes I feel like the tool I really need is a "stupid query log."
There are times when the ORM produces SQL that is not what I expect,
and I often don't realize this until I go and look at the slow query
log, which is usually after the project is already in some stage of
production or at least
On Tue, Jul 19, 2011 at 10:38 AM, Javier Guerra Giraldez wrote:
> On Tue, Jul 19, 2011 at 12:16 PM, David wrote:
> > This does duplicate
> > some functionality of RDBMSs but aggregating queries across multiple
> > databases is really convenient rather than having to go to each
> > database's log
On Tue, Jul 19, 2011 at 12:16 PM, David wrote:
> This does duplicate
> some functionality of RDBMSs but aggregating queries across multiple
> databases is really convenient rather than having to go to each
> database's logs.
i'd also like something like that to have better context. for
example,
I think it would be useful to be able to log all queries and/or some
"slow" subset of queries in production (DEBUG=False). I understand
clearly the reasoning why queries are currently only logged in debug
mode, but not all problems crop up in debug mode. This does duplicate
some functionality of RD
