It seems to me that "there should be one--and preferably only one--way to do it." This would entail having two ways.
Sometimes that makes sense if they're distinct enough things conceptually, but personally I don't see that case. Best Regards, Luke Sneeringer Sent from my iPhone. Forgive us our typos as we forgive those who typo against us. > On Jun 15, 2013, at 9:11 AM, Amir Rachum <nur...@gmail.com> wrote: > > Hi there, > > I'm not sure if this feature was discussed before (I've seen some mentions of > it when searching this group, but nothing definitive). > I have written a blog post regarding the reasons (and the suggested syntax) > to use this relationship, and would love some feedback > > http://blog.amir.rachum.com/post/53019452363/a-case-for-a-onetomany-relationship-in-django > > Thanks, > Amir Rachum > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
