Hello, here is a good article, which explain how to extend the django user- model. http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-model/
Bernd On Nov 18, 5:47 pm, radioflyer <[EMAIL PROTECTED]> wrote: > Hello, > > New Django user. > > I'm building an application to help manage departure scenarios for > elementary school students. One feature allows parents to login and > and make changes to their children's departure routine. ie. Instead of > "Get on your normal bus," they could change it to "Go to music lesson > with Mr. Smith." > > Just before school lets out, reports are distributed to the homeroom > teachers so they will know of any changes. > > I had set up related models Parent and Student. Then I got ready to > work on the authentication for the parents and thought maybe it would > be easier to set the parents up as 'Users' to take advantage of the > built in Django authentication structure. > > If I go this way, I will be limited in what fields I can associate > with Parents/Users unless I extend the built in Users model (can I?) > I'd like to be able to include some "convenience" fields (parent cell > phone, emergency phone, etc.) on the report. > > I'd appreciate some suggestions as to which way makes the most sense > from a Django point of view. Is there a Django "best practice" for > this? > > Thanks, > Dan Jewett --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
