Django's User Authentication Module is pretty dependent upon it's set of assumption, including that the User data would be stored in a specific table. Without any experience in this matter, I would assume it'd be a difficult task to try to modify it to use your own table. However, you can write your own Authentication Backend. Or, you could just do like Benedict mentioned and create a one-to-one relationship with your own UserProfile if you simply want to extend the User class. Also, check out 3rd party Authentication Backends. This stuff is documented really well in the Python Docs. Also, feel free to check out Python's source code directly.
On Thu, Oct 13, 2011 at 10:41 AM, Benedict Verheyen < benedict.verhe...@gmail.com> wrote: > On 13/10/2011 13:15, Jiss wrote: > > I am new to django. Can I use my own table (say) 'User' instead of > > 'auth_user' table (keeeping all other tables for django > > authentication ) ?. > > > > Why would you want to do that? > Keep everything standard and put the fields you want in a UserProfile > of your own where you store the extra information. > See the django doc: > > https://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users > > Cheers, > Benedict > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
