#27241: Annotate doesn't work with PostgreSQL views anymore
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql view | Triage Stage:
aggregate annotate | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jaap3):
Unfortunately I don't have a solution that would just make things work.
One of the underlying issues here is that Django has never officially
supported database views in the first place so I don't know how much
effort should be put into making this work again. The fact that this used
to work in the past was pure coincidence anyway.
Come to think of it, this problem might not just limited to database
views. I believe any (unmanged) model that hasn't set a `PRIMARY KEY`
constraint at the database level could trigger this issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/27241#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.cdb36b26574d80b373f7b166f19babb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
