#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 | Resolution:
Keywords: auth, core |
-----------------------------------+----------------------------------------
Comment (by [EMAIL PROTECTED]):
I'm not a django developer, of course, just a user, but I think it
shouldn't. As for me, the base class doesn't need to know anything about
it's subclasses.
Why retrieve an instances of subclasses trough ''User'''s API?
For example, you have just very simple ''User'' model, as I described
above. Then you subclassing an ''Employee'' model, that have additional
fields, like ''firstname'' and ''lastname''. You '''don't''' use the basic
model for typical site users' administration! You will add, change and
delete ''Employees'' trough admin interface instead!
In this case, there's no need to call ''Employee's'' fields and methods
trough ''User'' API, because you deal only with ''Employees'', wich of
course have full access to ''User's'' fields needed for authorization
purpouses.
So why the hell I need this simplyfied ''User'' class, if I get the same
model as in current django version as a result?!
Because it's more clear, logical and extensible. And this is a django-way.
:)
--
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
-~----------~----~----~----~------~----~------~--~---
