On 7/25/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > I realized a new way to extend user models, it is simpler than official > get_profile approach of django[1] as there is only one model to work with, > and relationships are kept on the right model, and gives a less hacky feel > than "replaces_module" method[2].
Personally, I'd disagree about it feeling "hacky"; it's using internal metasystem methods to pry open the model class and shove things into it, which is, well, hacky ;) Also, it's basically unusable on a multi-site installation. With AUTH_PROFILE_MODULE each site has its own settings file and can specify a different profile module, which means it's not possible for the different sites to interfere with each other's customizations. In this solution, however, every site shoves all its customization straight into the User model that's shared among them all, which raises a lot of ugly questions about what happens when those customizations collide with one another. Keeping per-site customization in a manageable, separate namespace is a good thing ;) -- "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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
