Re: Complex relationship for user profile

[Aaron Fay]

I'll try those, Peter, thanks for the response... Aaron Peter Rowell wrote: Failing a response to that one must mean I'm asking for something that is undoable. Uh, this isn't McDonald's. Slow/no response does not immediately equate to undoable. It more likely means that people who might have answered the question were doing something else (watching the debate, coding, sleeping, having a life). Regarding your question: Depending on the dynamics of your app, you might investigate the following: 1. If the profile is updated first and you want to propagate some changes to the associated User record, try overriding the save() method for UserProfile, do your thing, and then call super(UserProfile, self).save() to finish. 2. If the opposite is true (User is changed and you want to propagate to UserProfile), avoid the temptation to hack contrib/auth/models.py. Instead, use signals. See http://code.djangoproject.com/wiki/Signals. See http://www.martin-geber.com/weblog/2007/10/29/django-signals-vs-custom-save-method/ for a discussion on the difference between custom save and signals. 3. Modifying the admin can be useful, but can the data only be changed through the form? If yes, then proceed. If no, then option 1 or 2 is a better way to capture the change, regardless of the source of the change. HTH, Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---