#29650: Changes in refresh_from_db method
-------------------------------------+-------------------------------------
Reporter: Thomas Berdy | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: refresh_from_db | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
Can you simplify your steps to reproduce with some minimal models and
without `MyCustomSerializer` and the deepcopy stuff? It's difficult to
tell exactly what's happening in your code. Ideally, you could also
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#bisecting-a-regression bisect] to find the commit where the
behavior changed. 136bf5c2142ae3261669d02e2dd050c3141f7f2f perhaps.
--
Ticket URL: <https://code.djangoproject.com/ticket/29650#comment:1>
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/064.474756b57f163259e7337a2ab85aebbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
