On 8/9/06, Joe <[EMAIL PROTECTED]> wrote: > I know this is a bit "hackish", but it will work until model > inheritance is straightened out.
What people actually want is not "a subclass of User that has extra fields"; what people actually want is "User with extra fields". There's a big important difference there, because the auth system uses django.contrib.auth.models.User, and there is absolutely no way to make it use some other model -- even if that model is a subclass of User -- instead. We used to have 'replaces_module', but that was ugly and went away a long time ago and, God willing, will never come back. So despite popular misconception, model inheritance does not and will not provide any easier/better/more efficient way to extend the User model (as I noted in my blog entry about extending User). The fact that AUTH_PROFILE_MODULE and get_profile() were around when subclassing worked in the 0.90 and 0.91 releases should indicate that fact; building a separate model related to User is and probably always will be the best way to extend it. -- "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 -~----------~----~----~----~------~----~------~--~---
