#24215: Refactor of lazy model operations
-------------------------------------+-------------------------------------
Reporter: AlexHill | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
I'm working on refactoring the way relation fields are implemented in
Django (#24317). One part of the work is to store directly the remote
parts of fields in the remote model's _meta. This isn't that complex to do
when first creating the models, but when doing partial re-renders for
migrations we need some way to re-fire the equivalent of class-prepared
signal. The ticket contains a larger explanation of what I'm planning to
do. The last point in the plan is the troublesome case. Ideas welcome!
--
Ticket URL: <https://code.djangoproject.com/ticket/24215#comment:14>
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/066.d58622d882b5b7dd5ae09762ea334196%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
