Why do get_profile() and AUTH_PROFILE_MODULE exist, instead of just declaring the Profile to User relationship as OneToOne and using the auto-generated User.profile relationship?
I just changed my Profile's User relationship from ForeignKey to OneToOne (the docs say to use ForeignKey, not OneToOne--is this an error?) and it works fine. It does mean you can access the profile without knowing the name of the class, but you need to know the contents of the model to do anything with it anyway. Do user profiles predate reverse relationships? I'm just curious about the the design rationale here. -- Glenn Maynard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
