Hi, > On 8/9/06, Vance Dubberly <[EMAIL PROTECTED]> wrote: > > I very much want to subclass User as I have more than one kind of user > > and each has a different type of profile. > > Which is a different situation from probably 80% of the needs people > have for extending the User model.
I think I'm with the 20% just the extra fields is not enough in my case. I will need the ability to call my functions before and/or after the User object is saved in django user admin. For example somebody changes user's email in admin I want to call function that will report the new email address to a webservice. I guess the Foreign Key solution suggested by Joe would actually work here. Since the inline objects are getting saved with parents and I can just override the save of the inline object. However it still feels Hackish. As you can guess my auth/user system might actually span across multiple physical servers or at least parts of the user data will. Am I just better off writing my own auth system altogether or does anybody have an elegant idea how to easily extend the user system with own function calls? Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
