#25715: refresh_from_db fails to update null'ed ForeignKeys -------------------------------------+------------------------------------- Reporter: joshkel | Owner: timgraham Type: Bug | Status: closed Component: Database layer | Version: 1.8 (models, ORM) | Severity: Release blocker | 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 Tim Graham <timograham@…>): In [changeset:"8727dc8e951d0c3f4afc9cc2a5159fb651e5535c" 8727dc8]: {{{ #!CommitTicketReference repository="" revision="8727dc8e951d0c3f4afc9cc2a5159fb651e5535c" [1.9.x] Fixed #25715 -- Fixed Model.refresh_from_db() with ForeignKey w/on_delete=SET_NULL. Backport of 54e2e688e1cfbdb37dfa5dd3b3ffdf2af12b4423 from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/25715#comment:7> 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 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/065.2b655fdd94c1a092ec823e9d41462b3c%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.