Thanks ! Pretty clever :) Unfortunately it will not work with my application because I need to change the validator on username. Sounds like I have to use the 2nd solution until model subclassing works.
On Aug 13, 2:29 pm, Carl Karsten <[EMAIL PROTECTED]> wrote: > Grégoire wrote: > > Hello, > > > I would like to extend some functionnalities of contrib.auth, > > especially in the User model. > > > The objective is to do something clean without hacking django's source > > code. My first idea was to create a new auth application (e.g. myauth) > > and create a new User class in there extending the > > contrib.auth.models.User class. Unfortunately, it doesn't work at all: > > django does not find the other models obviously. I added them by hand, > > then added the relationships to have all the tables and finally > > realized that it doesn't work with the admin interface :( > > > So, what's the good way to add some fields to the User model and > > change some validators? Maybe the only solution is to copy the code > > from contrib.auth and contrib.admin into new applications and start > > from it... > > > Thanks in advance for any advices ! > > > Grégoire > > http://www.b-list.org/weblog/2006/06/06/django-tips-extending-user-model > > Carl K --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
