#15103: Django 1.2.4 breaks limit_choices_to for raw_id_fields
-------------------------------------------+--------------------------------
Reporter: natrius | Owner: nobody
Status: new | Milestone: 1.3
Component: django.contrib.admin | Version: 1.2
Resolution: | Keywords: blocker regression
send_mail email
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by russellm):
Ok - with @luke's help, I've discovered the flaw in my logic: just because
you have a list of Tours and associated leaders doesn't *necessarily* mean
that the status of each of those leaders is displayed publicly on the list
of Tours -- and in the example provided, it isn't.
The situation we have is an admin interface that allows me to know a list
of all available leaders, but won't let me know their status unless I try
to associate them with a Holiday -- in which case I am given the
restricted subset that meets the 'expert' criterion. Which strikes me as a
really bad (or at least unusual) piece of UX, but that's doesn't change
the fact that it's possible, and may have practical application in some
circumstances.
Objection dropped; filtering on value appears to be required, and the
patch seems fine to that end.
--
Ticket URL: <http://code.djangoproject.com/ticket/15103#comment:9>
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.
