#33312: Instances with deferred fields cannot be used for copying.
-------------------------------------+-------------------------------------
Reporter: Adam Sołtysik | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Sołtysik):
Ok, I understand that it might not make much sense to implement copying
instances with deferred fields. A warning in the docs would certainly be
helpful. Adding a more readable exception message (consistent for all the
cases) may also be worth considering, as sometimes it's not obvious that
our queryset has deferred fields, like when there's a custom manager
defined for a model. Especially the `DoesNotExist` exception in the last
two cases in very unclear.
--
Ticket URL: <https://code.djangoproject.com/ticket/33312#comment:3>
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/065.75873fd95cc0ce4e458ced1c2f6c71ea%40djangoproject.com.
