On Mar 24, 11:21 pm, Thierry Chich <thierry.ch...@gmail.com> wrote: > Le mercredi 24 mars 2010 16:53:12, Sandman a écrit : > > > Hi Derek, > > > One way to do this would be to create a proxy model that can be used > > throughout your project. > > > Check out > >http://docs.djangoproject.com/en/dev/topics/db/models/#proxy-modelsfor > > more info. > > Hi, > > This is what is said in one page, but in an other, it is suggested that you > just create your class with yours fields and put foreignkey on User. > > It work very well, indeed. > > http://docs.djangoproject.com/en/1.1/topics/auth/#topics-auth > see "Storing additional information about users"¶ > > > > > Take care, > > Rajiv. > > > On 3/24/10 7:44 AM, Derek wrote: > > > I am currently using UserProfile to create additional fields that are > > > needed for my users. > > > > I would like to be able to alter the existing User model to use the same > > > fields, but make some of them "required" (show up as bold on the form) > > > e,g, the first name and last name. How would I do that? > > > > Thanks > > > Derek >
Thierry Thanks, but I already am using the UserProfile for *additional* fields - I need to be able to change the behaviour of the *existing* fields in the auth_user (aka User). Derek -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
