Re: User model optional

You can - it's just Python, so you can do virtually anything - auth is
a contrib module, so you can just choose not to use it.
But the User model does a ton of work and is hooked into many other
modules - including all the base auth layer you might want to build
your custom authorization on top of.

might be better to port the data into the User model (maybe with a
related custom Profile class for extra profile info) and write a
facade and custom forms to present your preferred naming conventions
to the rest of your system?

just a thought...

On Nov 20, 2:55 pm, VB <vine...@gmail.com> wrote:
> I'm interested in porting a custom CMS from Rails to Django. We
> currently have a User model and I would like to keep it intact, keep
> naming conventions, etc. So, two questions:
>
> If I intend to write my own authentication, can I use my define my own
> User model? Or, am I better off naming the model something else?
>
> Thanks in advance.
>
> VB

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.