Re: contrib.auth.models.User and related_name on 'groups' attribute

2007-08-10 Thread PoBK
On Aug 9, 8:46 pm, Collin Grady <[EMAIL PROTECTED]> wrote: > group_obj.user_set.all() /is/ available :) Doh. I forgot about the _set thing... Moral of the story: don't code if you've not slept for 36 hours -- Richard --~--~-~--~~~---~--~~ You received this me

Re: contrib.auth.models.User and related_name on 'groups' attribute

2007-08-09 Thread Collin Grady
group_obj.user_set.all() /is/ available :) --~--~-~--~~~---~--~~ 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

contrib.auth.models.User and related_name on 'groups' attribute

2007-08-09 Thread PoBK
Hi guys, I'm just wondering if there is a rationale for leaving off the related_name attribute on the 'groups' field for the User model. I can't think of a reason against this? Surely it would be beneficial to have group_object.users.all() available? -- Richard --~--~-~--~~---