Hi, I'm not getting why you *have* to add fields to the User model to store data pertaining to the user. There is nothing in the proposal for pluggable user models that says you can never have a seperate model with a foreign key to the user model. It just means that you can define your user model the way you want it to be.
Why can't third party apps have a model with a foreign key to the user table with the pluggable models approach? I imagine you are right that every app and it's brother adding fields to the user model is not realistic but I don't think that anyone has proposed that. Certainly not me. The thing I want to be able to is define user models suitable for my project. Third party apps adding their own fields wasn't proposed by anyone AFAIK, nor was specifically requiring that you add them yourself. Some might require that your user has something like an 'email' field because that would be a common field across apps but app specific data can easily go on a seperate model included with the app that simply has a FK to user. You can then only fetch that data on requests that need it. I'm sorry but doing a JOIN every request is a BAD idea. You will run into problems there quickly and have no way out of it besides ditching auth completely (and thus all the thirdparty apps you use that depend on it). Assuming the user table and profile tables are small is awfully short sighted. Ian 2012/04/10 18:47 "Tom Evans" <tevans...@googlemail.com>: -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
