On 1/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I've seen a few posts that this was a bug where you cannot specify > order_by with a column from a foreign key ... > order_by(foreignkeytable__foreignkeycolumn) because it says table not > found. > > Does anyone know if there are plans to fix this...or if there is a work > around?
There are no specific plans that I am aware of (i.e., no schedule that says 'will be fixed by 25 Jan'). There was talk of a refactoring of query.py that was to address problems like this one, but the developer that was championing this cause (Malcolm) has been absent of late. Obviously, it is a bug, and it would be nice if Django had no bugs, but the core developers have limited time, and we spend it where we think it has the most benefit. If someone were to step up and fix this problem, it would probably find its way into the trunk fairly quickly (assuming it was a complete patch, of good quality, with unit tests, etc). Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
