Ahh okay. Yeah -- you'll most likely need to write your own custom
authentication backend to use the existing table.
https://docs.djangoproject.com/en/1.3/topics/auth/#writing-an-authentication-backend
Good luck!
On Wed, Oct 19, 2011 at 2:36 AM, Jisson Varghese <
jisson.vargh...@dexetra.com>
I want to do this since,The project I am handling(my first web project) is a
mobile version of a project ,there is already a user table in our
serverside.So avoid redundancy ,am not able to create a new table for users.
On Thu, Oct 13, 2011 at 8:11 PM, Benedict Verheyen <
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
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
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 ) ?.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
5 matches
Mail list logo
