On Sun, 2008-03-02 at 09:38 -0800, watusee wrote: > Thanks for you quick and helpful reply Malcolm! A few clarifications > if I may. I couldn't quite figure out how to connect what the admin > tool does to seeing queries in connection.queries. I can however see > the the offending query when I get an error in the admin. If I do see > a query that is not what I expect, do I have any recourse?
Not really. It just means that either your expectation is wrong or what Django is generating is wrong. Life's like that sometimes. > You also mentioned "bleeding from the eyeballs to fix something that > has a better solution" (I'd like to borrow that phrase, it could come > in handy in a myriad of situations :-)). Could you point me towards > the better solution? I feel like I might be missing something here and > I'd much prefer the better solution! I mean *I* was not going to do any the hard work to fix this fairly illogical ordering syntax in core when there is a better solution available to just treat it like normal filtering. Mixing database table names and model attribute names is really messy, so fixing any bugs is messy. Eventually the new syntax will become part of trunk. For now, you just have to wait a little while. Malcolm -- Works better when plugged in. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
