On Sun, 2006-06-04 at 12:29 +0200, Guillermo Fernandez Castellanos
wrote:
> Hi,
>
> First of all, thanks to both of you.
>
> Mmm... even if Olive's answer works, it's indeed, as he say, not very
> pythonic nor very django-like.
>
> On the other hand, I would not be very concerned about the fact that
> the developper must know the underlying database tablenames, as this
> already happen with other commands as the get() or the filter(). In
> deed, you can find in those commands arguments like
> table1__table2__name__exact.
Not quite. Chaining through related fields using filter(), for example,
is written as
Entry.objects.filter(blog__name__exact = 'fred')
Here, 'blog' is the field in the entry model and 'name' is the field in
the related 'Blog' model. There are no table names here, just model
names. Whereas the order_by() documentation explicitly talks about
database table names (which are of the form <app>_<model>). I cannot
think of another place (outside of extra(), which is "diving under the
covers" in any case) where you need more than the model and field names.
It's this slight inconsistency I am talking about.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
