James Bennett wrote: > Which I've never understood. Subclassing User, even when model > inheritance works again, will be probably the most difficult, least > efficient and least rewarding way of extending User...
But nobody knows this beforehand. The feature is called "subclassing" and looks like it should fit perfectly when one wants to add some additional fields for users. Again, having the solution with OneToOne relation scares newbies away because it's become a kind of common wisdom that OneToOne will be changed very drastically very soon and "all your code would burn". I was extending User model before I've read about the "profile" thing [1] and I did it in a way that seamed natural: created my own "User" and was trying to refer to it all over the place as ForeignKey. Now I realize that I've made a mistake because I have to go back and forth over this relation all over the code. I believe this is a common misconception. In short, my point is that newbies being Python programmers are familiar with extending classes but don't know about user's profiles supported in Django. [1]: http://www.b-list.org/weblog/2006/06/06/django-tips-extending-user-model --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
