On 9/19/07, James Bennett <[EMAIL PROTECTED]> wrote: > David Cramer has asked that Django's ORM lookup syntax be changed to > allow a single underscore for a foreign key lookup; in other words, > the following two examples would become equivalent: > > UserProfile.objects.get(user__id=3) #Currently works > UserProfile.objects.get(user_id=3) #Currently does not work
I second the notion of continuing to obscure the magical fields in general usage. Wherever reasonable, models should look and act exactly as they're defined in their classes. Drawing further attention to the fact that there are in fact "invisible" attributes will just cause more confusion, I would think. Anyway, I'm no expert on the matter, but that's my take on it. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
