#24607: Serialization (and deserialization) of MTI models doesn't work with 
natural
keys
-------------------------------------+-------------------------------------
     Reporter:  Denys Duchier        |                    Owner:  Tim
                                     |  Graham <timograham@…>
         Type:  Bug                  |                   Status:  closed
    Component:  Core                 |                  Version:  master
  (Serialization)                    |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  new => closed
 * owner:  (none) => Tim Graham <timograham@…>
 * resolution:   => fixed


Comment:

 In [changeset:"cb7860ccedb199cb221c9e084b5104978b246356" cb7860cc]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb7860ccedb199cb221c9e084b5104978b246356"
 Fixed #24607 -- Serialized natural keys in multi-table inheritance models.

 Thanks João Paulo Melo de Sampaio for the test.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/24607#comment:20>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.4fd07f70361cbeed65a9ec9644b747e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to