Hello Amir, you've mentioned only definiton of model. Yes, it looks interesting and definitely more readable. But definition of model is just the begining.
At database level, these models would be represented in the same way. (No difference) Working with models would be similar or even the same as it's now: ``member.group = band`` or ``band.members.add(member)`` Again, I don't see any difference. There would be probably some constraint when you try delete member of band which doesn't have any other members. Now, that could be implemented using pre_delete/post_delete signals. It looks for me that the only difference is in readability of models.py. What am I missing? Cheers, Tomas Ehrlich Dne Sat, 15 Jun 2013 08:11:53 -0700 (PDT) Amir Rachum <[email protected]> napsal(a): > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
