Django auth without "auth_*" tables

Posted by Travis Jensen on Stack Overflow See other posts from Stack Overflow or by Travis Jensen
Published on 2010-01-21T17:36:18Z Indexed on 2010/04/01 4:13 UTC
Read the original article Hit count: 618

Filed under:
|
|

We would like to use our own tables for user management instead of the Django "auth" tables. We already have database tables that include all of the relevant information our application needs but it isn't in the Django format. We would prefer not to have the information duplicated in two tables.

We would like to utilize the auth package, though, as there is some very nice functionality that we don't want to replicate.

I realize we could build our own auth backend, but that doesn't, as far as I can tell, remove the need for two sets of tables in this case.

Am I correct in assuming that we cannot do this? I have found no docs that discuss how to modify the underlying model that the auth package is using. The backend simply pre-populates the user object that would eventually be saved in the auth tables.

Thanks!

© Stack Overflow or respective owner

Related posts about django

Related posts about python