#28107: Can't perform annotation on related table when un-managed model is
backed
by a DB view
-------------------------------------+-------------------------------------
Reporter: powderflask | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: QuerySet.extra | 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 Simon Charette):
Jaap Roes,
At this point I'll take the issue to developers mailing list to gather
more feedback and give this issue more exposure.
It's true that it could be causing a performance regression for unmanaged
models in Django 2.0 relying on aggregation but since we've been
documenting such models should be used to interface with views for so long
I think there's still a point to be made about the fact the optimization
broke the public API.
Let's not forget that pre-Django 1.9 users were using ORM aggregation on
PostgreSQL just fine in most cases before the optimization landed and that
it's only an issue when a model contains large columns.
--
Ticket URL: <https://code.djangoproject.com/ticket/28107#comment:20>
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/069.638c0c009c2b40ee2a59a4ae30f217b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
