#35640: ModelMultipleChoiceField fail when the foreignkey remote model is a
child
class of anohter model
-------------------------------+--------------------------------------
Reporter: Omar BENHAMID | Owner: (none)
Type: Bug | Status: closed
Component: Forms | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Omar BENHAMID):
There is indeed an issue, the question is the use cas support it : is it
worth solving ?
Currently django-slick-report builds a search form using a
ModelMultipleChoiceField backed by a simple ForeignKey field (the aim is
to select mutliple values for an "OR-search"). The way values are genrated
for the choices of the widgets are the same only if the field is iterable
(so one to many but not many to one) and this often works well except when
model inheritence is used.
I can provide a test case but the question before is : is this usage
supported ? Shall we try to make this part more robust in django?
--
Ticket URL: <https://code.djangoproject.com/ticket/35640#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701911cf16aaf-977a9b41-54cd-47c9-86f0-826fecfe77b0-000000%40eu-central-1.amazonses.com.
