Hey Derek, On Sat, 2009-01-24 at 04:58 -0800, dwil...@gmail.com wrote: > Ramiro, > > Thanks very much - I knew I must have been overlooking something. > Adding __exact did the trick nicely.
If you want to open a ticket about that, it might be worth us taking another look at the error reporting. We can (probably) detect that a "year" field is one of the possibilities and clarify the error message. I would probably avoid doing automatic disambiguation, since somebody will then end up trying to mistakenly do a "__year" lookup and have it follow the "year" field, which just flips the confusion, but we could at least say "do you mean to follow the year field? Try adding __exact" or something similar. A bit of extra processing time spent there (working out what might be possible) won't hurt, since it's only in the error path and should never occur in production runs. 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
