Ok. That's what I thought, but just wanted to make sure I wasn't missing something somewhere. Wasn't sure if this was a special case, as the AUTH_PROFILE_MODULE is used for get_profile, perhaps it was used to save/ sync the models.
Thanks again! -C On Jul 9, 11:58 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 7/9/07, Chris Kelly <[EMAIL PROTECTED]> wrote: > > > Or do I have to manually manage saving both objects when making a > > change? If so, what's the preferred way to do this? by managing the > > profile via the user object, or by managing the user object via the > > profile (overriding the profile save method)? > > You must manually create and manually save the related profile object, > just as you'd have to manually create and manually save any other type > of related object. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
