On 9/9/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > I've found the problem. > > Create an Article and Photo object in the admin view. Then, the following in > the shell: > > >>> from testproject.mytest.models import Photo > >>> Photo.objects.all()[0].article_set.all() > throws Attribute Error > > but, if you then run: > > > >>> from testproject.mytest2.models import Article > >>> Photo.objects.all()[0].article_set.all() > [<Article: asdf>] > > Until you import Article, the related objects for Photo aren't populated. > > This is a bit of a 'slaps forehead' moment for me - it's kinda obvious if > you know the internals. However, I agree that it isn't obvious for end > users. This is worth logging as a bug (if you would be so kind) - both in > terms of 'this should be documented more clearly', and 'all related objects > should automatically populated'. The first is easy to fix; I'm not so sure > about the second. >
Sounds good, thanks so much! Here's something I *just* found though: If instead of: >>> from testproject.mytest.models import Photo >>> Photo.objects.all()[0].article_set.all() you do: >>> from testproject.mytest.models import Photo >>> x = Photo.objects.get(id=1).article_set.all() it all works perfectly! So if you do a get() instead of an all(), the 'article_set' attribute gets created. I've created a patch (http://code.djangoproject.com/ticket/2684) that mentions all of this. Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
