Re: [Django] #30247: ModelMultipleChoiceField Bug - Initial Values has to be in queryset, does not make sense

[Django]

#30247: ModelMultipleChoiceField Bug - Initial Values has to be in queryset, 
does
not make sense
-+-
 Reporter:  Josef Korbel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  2.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
  ModelMultipleChoiceField   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 You've misunderstood what's going on here. `queryset` in this case means
 the set of allowed values. All values, whether initial or not, must be in
 `queryset`.

 If you're not clear on this please see
 TicketClosingReasons/UseSupportChannels.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.82ea47cd972cec71fdb24884ace5ac5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30247: ModelMultipleChoiceField Bug - Initial Values has to be in queryset, does not make sense

[Django]

#30247: ModelMultipleChoiceField Bug - Initial Values has to be in queryset, 
does
not make sense
-+-
 Reporter:  Josef Korbel |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  ModelMultipleChoiceField   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Josef Korbel):

 * component:  Uncategorized => Forms
 * type:  Uncategorized => Bug


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.ef456fae6993e44cf1c15b7018a363a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30247: ModelMultipleChoiceField Bug - Initial Values has to be in queryset, does not make sense

[Django]

#30247: ModelMultipleChoiceField Bug - Initial Values has to be in queryset, 
does
not make sense
-+-
   Reporter:  Josef  |  Owner:  nobody
  Korbel |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  2.1
  Uncategorized  |   Keywords:
   Severity:  Normal |  ModelMultipleChoiceField
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When using ModelMultipleChoiceField, the initial values need to be in the
 queryset, or the widget will be empty. As my queryset is collection of
 unassigned objects, my initial will never by in my queryset, thus making
 this undoable for me, here are more details on SO.

 https://stackoverflow.com/questions/54941814/django-
 modelmultiplechoicefield-1n-initial/54998957#54998957

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/054.5dc2ac1d58d6248b2e5656a07b63feae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.