#2562: Too much fields in User model
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Core framework | Version: 0.95
Severity: normal | Keywords: auth, core
-----------------------------------+----------------------------------------
I think there's too much fields in base ''User'' model.
The only '''required''' fields for authorization purposes are
''username'', ''password'' and, possibly, ''is_active'' flag. So I think
others should be removed (Yes, I know that other fields are optional). Why
store in basic athentification model some additional data that isn't
needed for athentification?
With the new cool inheritance features you work on, it will be quite easy
to extend base class with new fields.
If you think that firstnames, lastnames and e-mails are very common,
you're defenitely right. So you could make some model (''Staff'', for
example), wich extends basic ''User'' with this fields and include it in
django distribution. So if one needs just auth(entification|thorization),
he would use base ''User'' class. Other would use built-in ''Staff''
class. And someone else would derive a custom class from basic ''User''
with exactly such fields, as he needs.
Even if part of my users are robots, that have only ''model'' and
''version'' parameters, part of them are humans with common ''firstname''
and ''lastname'' and another part are programmers wich have only
''email'', I could build a custom model for each of them, not giving up
the power of django's athentification system.
--
Ticket URL: <http://code.djangoproject.com/ticket/2562>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
