#29195: Postgres Regression, annotating Exists through a OuterRef query. -------------------------------------+------------------------------------- Reporter: Oli Warner | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 2.0 (models, ORM) | Severity: Release blocker | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Simon Charette):
* cc: Simon Charette (added) * severity: Normal => Release blocker * stage: Unreviewed => Accepted Comment: Hey Oli, thank you for your report! I'm not sure what is at play here but if you bisected the issue to this commit and it's possible to work around it using an explicit `output_field` it's probably an issue with expression cloning. Would it be possible to include the fully generated queries that crashes on PostgreSQL, it should be doable using the ` --debug-sql` flag to the test command. I didn't reproduce but accepting based on the detailed error report. -- Ticket URL: <https://code.djangoproject.com/ticket/29195#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/067.9e1c591b7ed720a8ceb7d3f8b7afb084%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.