On 3/26/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > It (logging all queries), is also just not something that's usually that > useful. If you are trying to track down a particular problem, a more > targeted approach and some experiments at the interactive prompt, > combined with printing out connection.queries normally suffices. If you > want to see what is sent to the database, connection.queries isn't the > accurate answer in any case, because it doesn't show what the database > wrapper does as far as quoting goes -- for that, you should be turning > on your database's query logging functionality to see the raw data.
I mostly just needed to see what the Q() thingy was doing with my and/or filter (chain) logic. -- Greg Donald http://destiney.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
