I have searched through the dev list and couldn't find anything relating to the specific thing I am trying to do. I also am aware that both QuerySet and OneToOne fields are in some sort of flux right now.
QuerySet is being completely refactored, and I will of course wait for that (like my admin changes) to drop before trying to come up with a patch. OneToOne field has also been pending changes for about forever now and I don't know exactly what's going on with it. So this post is to start a dialog about whether we can follow OneToOne relationships in a bi-directional manner and what the current plans are. Assume two models, User and Address. For some reason I like to store User and Address separately, perhaps because of update and select patterns or I just like having the data partitioned into two tables. Let's also assume that the OneToOne field exists in Address, it seems that there should be a way to pull in the address information from the User manager without resorting to hacks. Can anyone come up a reason that OneToOne fields should not be optionally automatically followed? Anyone for this support? I have done a good deal of cruising around the django.db package and I think I could add something. But this is a rather large core change and I am sure people have feelings about it. Looking forward to hearing from everyone, Trey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
