On Apr 7, 10:47 am, Julien Phalip <jpha...@gmail.com> wrote:
> Hi Matt, > > Do you think this could be related > tohttp://code.djangoproject.com/ticket/11448 > ? > > If so, do the patches attached to that ticket help resolve your issue? > > Thanks, > > Julien Hi Julien, Thanks for your reply - from a quick squint at that ticket I don't think it's related (options._name_map was populated with current information, it's just that map doesn't have sufficient information to allow setup_joins to differentiate between the reverse of O2O and the reverse of ForeignKey). As you can see from a reply I've just made to Russ I think the problem has gone away in Django 1.3 anyway (or at least it's been masked by another change, so I can now use reverse O2O in values and values_list with 1.3 without getting an error). Regards, Matt -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
