#31863: FK field caching behavior change between 1.11.x and 2.x
-------------------------------------+-------------------------------------
     Reporter:  Gert Burger          |                    Owner:  Gert
                                     |  Burger
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  2.2
  (models, ORM)                      |
     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
-------------------------------------+-------------------------------------

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

 In [changeset:"85c47b9a734365a84e56470d96fbe0fdb3b7a8b3" 85c47b9a]:
 {{{
 #!CommitTicketReference repository=""
 revision="85c47b9a734365a84e56470d96fbe0fdb3b7a8b3"
 [3.1.x] Fixed #31863 -- Prevented mutating model state by copies of model
 instances.

 Regression in bfb746f983aa741afa3709794e70f1e0ab6040b5.

 Backport of 94ea79be137f3cb30949bf82198e96e094f2650d from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31863#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f34b42a6d305f14168e4db43ce00fe08%40djangoproject.com.

Reply via email to