#28107: Can't perform annotation on related table when relation between tables
not
on primary key
-------------------------------------+-------------------------------------
Reporter: powderflask | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: QuerySet.extra | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by powderflask):
This may have to do with one of the original models drawing data from a
View - found this:
" The feature of Postgres to be able to use the primary key of a table
with GROUP BY and not need to add the other columns of that table in the
GROUP BY clause is relatively new and works only for base tables. The
optimizer is not (yet?) clever enough to identify primary keys for views,
ctes or derived tables."
https://dba.stackexchange.com/questions/88988/postgres-error-column-must-
appear-in-the-group-by-clause-or-be-used-in-an-aggre
I will try to reproduce this.
--
Ticket URL: <https://code.djangoproject.com/ticket/28107#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/069.40a9b8c735d3582d436a1674c4148c57%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
