#28621: Crash in QuerySet.annotate() with OuterRef -------------------------------------+------------------------------------- Reporter: Дилян Палаузов | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.11 (models, ORM) | Severity: Normal | Resolution: Keywords: QuerySet.extra | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Leo Antunes):
* cc: Leo Antunes (added) Comment: Another slightly simpler example of the same problem, using a model that only has a pk: {{{#!python SomeModel.objects.annotate(mod=Subquery(SomeModel.objects.filter(pk=OuterRef('pk')%2).values('pk'))) }}} Simply removing "%2" is enough to make it work (though not with the expected results, of course): {{{#!python SomeModel.objects.annotate(mod=Subquery(SomeModel.objects.filter(pk=OuterRef('pk')).values('pk'))) }}} -- Ticket URL: <https://code.djangoproject.com/ticket/28621#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 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/072.744ca6c4e72c215bbe47eb097987db21%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.