If I am understanding correctly now, does this mean I have to manage the creation of the user profile object (and also any other classes tied to a user) when I create the user? From what I can tell it looks like I'll need to have a create user method that will handle creating the user, and instantiating any other classes associated ( e.g. the profile class). Once it's created though, it shouldn't be an issue. Sound about right?
thanks again for the help!
-Chris
On 8/9/06,
James Bennett <[EMAIL PROTECTED]> wrote:
On 8/9/06, Chris Kelly <[EMAIL PROTECTED]> wrote:
> and it appears that using a one-to-one mapping (the
> article's preferred method) is discouraged.
I'm launching a campaign to have that line purged from the official
documentation, with extreme prejudice. OneToOneField isn't going away
and, AFAIK, isn't changing in a way which would actually break this
usage. OneToOne works. AUTH_PROFILE_MODULE works. get_profile() works.
Go to town with them.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
