#13667: Multiple profile models via AUTH_PROFILE_MODULES (proposal)
-------------------------------------+--------------------------------------
Reporter: humanfromearth | Owner: nobody
Status: closed | Milestone:
Component: Contrib apps | Version: 1.2
Resolution: wontfix | Keywords: user auth profile
multiple
Stage: Unreviewed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
-------------------------------------+--------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
My preference would be to deprecate the use of AUTH_PROFILE_MODULES, not
enhance it.
The related object manager for OneToOne fields already cache the remote
object, so there isn't any caching benefit to had here -- _profile_cache
is a historical artefact.
On top of that, you appear to be proposing that we modify get_profile so
that it might return multiple objects, depending on the value of a
setting.
Marking wontfix. I can't say I'm a fan of this proposal. Feel free to
start a discussion on django-dev if you want to advocate for this idea.
--
Ticket URL: <http://code.djangoproject.com/ticket/13667#comment:4>
Django <http://code.djangoproject.com/>
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?hl=en.
