> Judging from the comments on that ticket, I think it's a slightly > different issue; #2210 deals with fetching the Options class of the > wrong model when the related field has 'db_column' set; in that case, > it appears Django is generating the correct table list for the query, > but not the correct column list. In #2076, which I think is what's > going on here, Django generates the right column list, but has the > wrong table list. I don't think these are related.
You may be right, I looked at both tickets when I searched for a fix before I wrote one myself and I think I submitted the patch on the wrong ticket. I thought they were related then but maybe not. The patch in #2210 should be for #2076. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
