#34620: Serialization of m2m relation fails with custom manager using
select_related
-------------------------------------+-------------------------------------
     Reporter:  Martin Svoboda       |                    Owner:  Mariusz
                                     |  Felisiak
         Type:  Bug                  |                   Status:  closed
    Component:  Core                 |                  Version:  4.2
  (Serialization)                    |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"87a4cd559bc47a53c717a45a8b0a181681fe8a32" 87a4cd5]:
 {{{
 #!CommitTicketReference repository=""
 revision="87a4cd559bc47a53c717a45a8b0a181681fe8a32"
 [4.2.x] Fixed #34620 -- Fixed serialization crash on m2m fields without
 natural keys when base querysets use select_related().

 Regression in 19e0587ee596debf77540d6a08ccb6507e60b6a7.

 Thanks Martin Svoboda for the report.
 Backport of f9936deed1ff13b20e18bd9ca2b0750b52706b6c from main
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34620#comment:6>
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/0107018887bf3d84-aa3153bf-364f-4a56-b563-509ba17f4bb8-000000%40eu-central-1.amazonses.com.

Reply via email to