In the documentation I see that there are Many-To-One Fields, Many-To-Many Fields and One-To-One Fields. What about a One-To-Many Field? You might now say that this is completely pointless since a Many-To-One Field reversed is basically what I want. But I'd say that in some cases it makes more sense to define a One-To-Many Field (because it makes more sense to do it in Model A instead of Model B or whatever). One of the reasons I would like to see this is that as it is now you cannot directly edit reversed-relations through the admin page. You always have to go 'forward'. With a One-To-Many Field the user could choose in which Model he would like to edit the relationship on top on having the possibility to keep his code more readable because of the choice of Model where the relation is defined.
Related to this is that I'd say it would be favorable if reversed relationships could be edited through the admin page by default. --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
