On Sat, 2008-03-01 at 20:02 -0800, watusee wrote: > Using the manual Many to Many model as follows in revision 7188 [...]
> ######################################### > > I've done a lot of searching but can't quite figure out if this is > something that: > > a) Should work in said revision and I'm doing something wrong Looks like it probably should work. However, there seem to be a number of little bugs here, so it's mostly a case of "try and see". Use the "manage.py shell" interactive prompt to import your Book_Int model and create a queryset. Then have a look at the generated SQL (see the FAQ for how to do that) and see if it's what you expect. > b) Will be added in a queryset refactoring update That format of ordering will still work in queryset-refactor (and after the merge), but it will have all the same bugs as it does now, because it's practically impossible to fix. So I'm not breaking anybody's code that is already working, but I'm also not interested in bleeding from the eyeballs to fix something that has a better solution. In queyrset-refactor, you can do ordering = ['book__name'], just like a filter parameter. It's one less piece of syntax to have to remember and you don't need to try and work out what the database table name is. > c) Will be added in a newforms update Entirely unrelated to newforms, so no. Regards, Malcolm -- Atheism is a non-prophet organization. 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 -~----------~----~----~----~------~----~------~--~---
