#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 collinanderson):
Hi Alex,
Do you have example of why you would need two models? What real-world
problem are you trying to solve? :)
I think add_lazy_relations is one of those private APIs that may have a
lot of use, so if we're going to change it I just want to make sure it's
worth it. :)
Thanks,
Collin
--
Ticket URL: <https://code.djangoproject.com/ticket/24215#comment:4>
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.578b897afa6e18e60a3d3086ca99897e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
