#32673: Nested Q() objects raises ProgrammingError on PostgreSQL and Oracle.
-------------------------------------+-------------------------------------
Reporter: Charles Lirsac | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: postgresql oracle q | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"170b006ce82b0ecf26dc088f832538b747ca0115" 170b006c]:
{{{
#!CommitTicketReference repository=""
revision="170b006ce82b0ecf26dc088f832538b747ca0115"
Fixed #32673 -- Fixed lookups crash when comparing against lookups on
PostgreSQL.
Regression in 3a505c70e7b228bf1212c067a8f38271ca86ce09.
Nonlitteral right-hand-sides of lookups need to be wrapped in
parentheses to avoid operator precedence ambiguities.
Thanks Charles Lirsac for the detailed report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32673#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.6022b3786f1069415de139a85e4e7e9f%40djangoproject.com.
