On Tuesday, May 19, 2015 at 8:18:24 AM UTC-6, Ilya Kazakevich wrote: > > > I am really unhappy with idea of using custom user model. >> >> Why? >> >> If it's because this is an existing project and the prospect of >> migrating your existing data to a custom user model is daunting, I >> totally understand that. It's doable, but hard. >> > Yes, this project already deployed and has some data. Sure I can solve > this, but I feel that changing user model will make my app less reusable. >
I don't think "will make my app less reusable" is a valid reason to avoid a custom User model. A lot of thought went into the custom User model system to ensure that it preserves reusability. That's why things like `django.contrib.auth.get_user_model()` and friends exist. > But I will probably stay with new model. There is something wrong with > Django in this area. There should be some easy and elegant way to add one > field to auth_user. I wonder why Django developers do not care about it. > Django developers do care about the problem, and the preferred solution (after many years of discussion) is the custom User model. I believe that it's a better solution than introducing a hacky way to monkeypatch fields onto a built-in model. I think every Django project should use a custom User model. Carl -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d2f5e133-47a4-4255-a016-03d4b8a14d5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
